Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release 0.29.0 #525

Merged
merged 2 commits into from
Jul 12, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 12, 2024

🤖 I have created a release beep boop

0.29.0 (2024-07-12)

Features

  • parallelize linking, unlinking and installing (#524) (f0734e6)
  • update package manager versions (#492) (3e3b046)

Bug Fixes

  • replace npm registry domain in tarball URL (#502) (db6fae5)
  • selectively import required semver functions (#511) (e7ad533)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--corepack branch from af1b904 to 4468ed3 Compare July 12, 2024 08:47
@github-actions github-actions bot changed the title chore(main): release 0.28.3 chore(main): release 0.29.0 Jul 12, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--corepack branch from 4468ed3 to 265a5aa Compare July 12, 2024 12:43
@github-actions github-actions bot force-pushed the release-please--branches--main--components--corepack branch from 265a5aa to f897275 Compare July 12, 2024 12:59
@aduh95 aduh95 merged commit aa6fd83 into main Jul 12, 2024
13 checks passed
@aduh95 aduh95 deleted the release-please--branches--main--components--corepack branch July 12, 2024 22:30
Copy link
Contributor Author

🤖 Release is at https://github.com/nodejs/corepack/releases/tag/v0.29.0 🌻

@wojtekmaj
Copy link
Contributor

Whoops! Release failed. Seems like npm didn't consume the token correctly: https://github.com/nodejs/corepack/actions/runs/9914895226/job/27394821571

@wojtekmaj
Copy link
Contributor

We may need a token in npm that specifically has a type of "Automation" 🤔

@aduh95
Copy link
Contributor

aduh95 commented Jul 13, 2024

I struggle to find where npm documents the env variable it uses

@wojtekmaj
Copy link
Contributor

It is NODE_AUTH_TOKEN. This works for me:
https://github.com/wojtekmaj/react-pdf/blob/main/.github/workflows/publish.yml

So my assumption is that something is wrong with the token itself, not the way we're passing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants