Skip to content

chore: release 6.3.1 - #593

Merged
lukekarrys merged 1 commit into
release/v6from
release-please--branches--release/v6
Jul 10, 2023
Merged

chore: release 6.3.1#593
lukekarrys merged 1 commit into
release/v6from
release-please--branches--release/v6

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

6.3.1 (2023-07-10)

Bug Fixes


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Jul 10, 2023

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/node-semver/actions/runs/5511982240

Force CI to Update This Release

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

gh workflow run release.yml -r release/v6 -R npm/node-semver -f release-pr=593

Release Checklist for v6.3.1

  • 1. Checkout the release branch and test

    gh pr checkout 593 --force
    npm update
    npm test
    gh pr checks 593 -R npm/node-semver --watch
  • 2. Publish

    npm publish 
  • 3. Merge release PR

    gh pr merge 593 -R npm/node-semver --rebase
    git checkout release/v6
    git fetch
    git reset --hard origin/release/v6
  • 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 -R npm/node-semver $(gh run list -R npm/node-semver -w release -b release/v6 -L 1 --json databaseId -q ".[0].databaseId")
    

@lukekarrys
lukekarrys merged commit 44d27bc into release/v6Jul 10, 2023
@lukekarrys
lukekarrys deleted the release-please--branches--release/v6 branch July 10, 2023 22:38
@github-actions

github-actionsBot commented Jul 10, 2023

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto 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.

1 participant

@lukekarrys