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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: release 4.3.1 #206

Merged
merged 1 commit into from Sep 19, 2022
Merged

chore: release 4.3.1 #206

merged 1 commit into from Sep 19, 2022

Conversation

github-actions[bot]
Copy link
Contributor

馃 I have created a release beep boop

4.3.1 (2022-09-19)

Bug Fixes


This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Contributor Author

github-actions bot commented Sep 19, 2022

Release Manager

Release Checklist for v4.3.1

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    git checkout release-please--branches--main
    git reset release-please--branches--main --hard
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-4

    make publish
  • 5. Set dist-tag to published version

    Warning:
    NOT FOR PRERELEASE: Do not run this step for prereleases

    Note:
    You can optionally install via the version to see how it runs locally before tagging.

    Optionally install via version:

    npm i -g npm@4.3.1

    Set version to latest dist tag:

    node . dist-tag add npm@4.3.1 latest
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout main
    git pull
  • 7. 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 -L 1 --json databaseId -q ".[0].databaseId")
    
  • 8. Post on Twitter

    New @npmjs release: 4.3.1!
    
    https://github.com/npm/template-oss/releases/tag/v4.3.1
    
    Release details...
    
  • 9. Open nodejs/node PR to update npm to latest

    Warning:
    NOT FOR PRERELEASE: Do not run this step for prereleases

    Sync our npm/node fork with the nodejs/node upstream:

    gh repo sync npm/node --source nodejs/node --force

    Trigger the Create CLI Deps PR action:

    gh workflow run create-cli-deps-pr.yml

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 12e340c to 2c8b73f Compare September 19, 2022 08:16
@lukekarrys lukekarrys merged commit 4bbb731 into main Sep 19, 2022
@lukekarrys lukekarrys deleted the release-please--branches--main branch September 19, 2022 08:20
@github-actions
Copy link
Contributor Author

馃 Release is at https://github.com/npm/template-oss/releases/tag/v4.3.1 馃尰

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.

None yet

1 participant