Skip to content
New issue

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

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

Already on GitHub? # to your account

chore: release 10.0.0 #105

Merged
merged 1 commit into from
Oct 18, 2022
Merged

chore: release 10.0.0 #105

merged 1 commit into from
Oct 18, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 21, 2022

🤖 I have created a release beep boop

10.0.0 (2022-10-18)

⚠️ BREAKING CHANGES

  • x and x@ now return the same spec as x@*
  • npm-package-arg is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0

Features

Bug Fixes

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Contributor Author

github-actions bot commented Sep 21, 2022

Release Manager

Release workflow run: https://github.com/npm/npm-package-arg/actions/runs/3274124672

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r main

Release Checklist for v10.0.0

  • 1. Checkout the release branch and test

    gh pr checkout 105 --force
    npm i
    npm test
    gh pr checks --watch
  • 2. Publish

    npm publish 
  • 3. Merge release PR

    gh pr merge --rebase
    git checkout main
    git fetch
    git reset --hard origin/main
  • 4. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -b main -L 1 --json databaseId -q ".[0].databaseId"`
    

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 6667d48 to 3abc4d6 Compare September 21, 2022 00:39
@github-actions github-actions bot force-pushed the release-please--branches--main branch 4 times, most recently from 296b796 to 526002b Compare September 30, 2022 04:38
@github-actions github-actions bot force-pushed the release-please--branches--main branch 4 times, most recently from f56bd9d to 4d59736 Compare October 12, 2022 20:46
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from 76d7f32 to aab29de Compare October 14, 2022 20:32
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from d67d43c to f4c4c68 Compare October 18, 2022 14:05
@github-actions github-actions bot force-pushed the release-please--branches--main branch from f4c4c68 to e24d110 Compare October 18, 2022 14:06
@wraithgar wraithgar merged commit ad7b36f into main Oct 18, 2022
@wraithgar wraithgar deleted the release-please--branches--main branch October 18, 2022 14:14
@github-actions
Copy link
Contributor Author

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

Successfully merging this pull request may close these issues.

1 participant