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.0.4 #111

Closed
wants to merge 1 commit into from
Closed

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 4, 2023

馃 I have created a release beep boop

4.0.4 (2024-04-21)

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

github-actions bot commented Dec 4, 2023

Release Manager

Release workflow run: https://github.com/npm/bin-links/actions/runs/8774082649

Release Checklist for v4.0.4

  • 1. Approve this PR

    gh pr review 111 -R npm/bin-links --approve
  • 2. Merge release PR 馃毃 Merging this will auto publish 馃毃

    gh pr merge 111 -R npm/bin-links --squash
  • 3. 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/bin-links $(gh run list -R npm/bin-links -w release -b main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from e2907b6 to 45a81fa Compare December 7, 2023 22:31
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 45a81fa to 1a53b17 Compare April 21, 2024 16:37
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 1a53b17 to 0f36259 Compare April 21, 2024 16:38
@lukekarrys lukekarrys closed this May 3, 2024
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