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

Release v0.13.1 #9092

Merged
merged 3 commits into from Jul 6, 2022
Merged

Release v0.13.1 #9092

merged 3 commits into from Jul 6, 2022

Conversation

aschmahmann
Copy link
Contributor

@aschmahmann aschmahmann commented Jul 6, 2022

Patch Release Checklist

This process handles patch releases from version vX.Y.Z to vX.Y.Z+1 assuming that vX.Y.Z is the latest released version of go-ipfs.

  • Get temporary permissions to force-push to release-* branches (@guseggert is this needed, doesn't seem like it. I think this was just for last time)
  • Fork a new branch (release-vX.Y.Z) from release and cherry-pick the relevant commits from master (or custom fixes) onto this branch
    • Use git cherry-pick -x so that the commit message says (cherry picked from commit ...)
  • Make a minimal changelog update tracking the relevant fixes to CHANGELOG, as its own commit e.g. docs: update changelog vX.Y.Z+1
  • version string in version.go has been updated (in the release-vX.Y.Z+1 branch), as its own commit.
  • Make a PR merging release-vX.Y.Z+1 into the release branch
    • This may be unnecessary, e.g. for backports
  • Tag the merge commit in the release branch with vX.Y.Z+1 (ensure the tag is signed)
  • Upload to dist.ipfs.io
    1. Build: https://github.com/ipfs/distributions#usage.
    2. Pin the resulting release.
    3. Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
    4. Ask the infra team to update the DNSLink record for dist.ipfs.io to point to the new distribution. Not necessary, taken care of by CI after merging into master (https://github.com/ipfs/distributions/blob/6e06450dcf68d9749bb7d7092135a16e8271d276/.github/workflows/main.yml#L154)
  • cut a release on github and upload the result of the ipfs/distributions build in the previous step.
  • Announce the Release:
    • On IRC/Matrix (both #ipfs and #ipfs-dev)
    • On discuss.ipfs.io
  • Release published
  • Cut a new ipfs-desktop release
  • Merge the release branch back into master, ignoring the changes to version.go (keep the -dev version from master).

@aschmahmann aschmahmann marked this pull request as ready for review July 6, 2022 13:47
@aschmahmann aschmahmann requested a review from lidel as a code owner July 6, 2022 13:47
Copy link
Contributor

@Jorropo Jorropo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aschmahmann aschmahmann merged commit 8ffc7a8 into release Jul 6, 2022
BigLep added a commit that referenced this pull request Jul 6, 2022
These updates are based on items from #9092
@BigLep
Copy link
Contributor

BigLep commented Jul 6, 2022

We are improving the template in #9095 based on this release.

hacdias pushed a commit to ipfs/boxo that referenced this pull request Jan 27, 2023
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.

None yet

3 participants