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.

Sign up for GitHub

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

Chore/release go ipfs v0.12.2 v0.11.1 #679

Merged
merged 2 commits into from
Apr 8, 2022
Merged

Chore/release go ipfs v0.12.2 v0.11.1 #679

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dfc5a70
build: bump to building with 1.16.15
aschmahmann Apr 8, 2022
f4160a5
chore: release go-ipfs v0.12.2 and v0.11.1
aschmahmann Apr 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .tool-versions
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
nodejs 16.2.0
golang 1.16.12
golang 1.16.15
2 changes: 1 addition & 1 deletion dists/go-ipfs/current
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v0.12.1
v0.12.2
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This had to be done manually/carefully to avoid v0.11.1 being here. Filed for tracking purposes #680

2 changes: 2 additions & 0 deletions dists/go-ipfs/versions
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,8 @@ v0.10.0
v0.11.0-rc1
v0.11.0-rc2
v0.11.0
v0.11.1
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure if it matters where in this file v0.11.1 goes, i.e. if it should be in semver order or chronological order.

The tooling uses chronological ordering but I can't tell if that's a bug or not.

Copy link
Member

Choose a reason for hiding this comment

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

If someone cares, there is date field in dist.json created during the build, it indicates when release was published.

v0.12.0-rc1
v0.12.0
v0.12.1
v0.12.2