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

🚀 9.3.0-alpha.4 #7489

Merged
merged 1 commit into from
Jun 5, 2024
Merged

🚀 9.3.0-alpha.4 #7489

merged 1 commit into from
Jun 5, 2024

Conversation

insomnia-infra
Copy link
Contributor

@insomnia-infra insomnia-infra commented Jun 5, 2024

WARNING: Do not merge this PR. This is an automated release PR. It should be released using the "Publish" workflow.

Download release artifacts here

Steps for Publish:

You can update the changelog.md in this branch, run git log to get the latest changes:

git log --no-merges --oneline --pretty=format:'* %s by @%an' --since="<last release tag>" --until="release/9.3.0-alpha.4"

When ready to publish, trigger Publish workflow with these variables:

  • Release version (version): 9.3.0-alpha.4

Alternatively, you can trigger the workflow from Github CLI:

gh workflow run release-publish.yml -f version=9.3.0-alpha.4 --repo Kong/insomnia

Release notes will be generated automatically based on the commit messages during publish. Remove any unwanted notes manually afterwards.

Conflicts? Merge branch step failed on the publish workflow? Try this...

Run locally:

# Make sure git remote is Kong/insomnia...

git checkout develop
git merge --no-ff release/<replaced with version>

# Solve merge conflicts ...
# If there's package-lock conflicts, run `npm install` and commit the package-lock changes

git push

@insomnia-infra insomnia-infra merged commit a7a0854 into develop Jun 5, 2024
11 checks passed
@insomnia-infra insomnia-infra deleted the release/9.3.0-alpha.4 branch June 5, 2024 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants