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

Bump version to 4.1.1 #699

Merged
merged 4 commits into from
Nov 7, 2022
Merged

Bump version to 4.1.1 #699

merged 4 commits into from
Nov 7, 2022

Conversation

oguzkocer
Copy link
Contributor

@oguzkocer oguzkocer commented Nov 4, 2022

This is my first release after the CHANGELOG.md introduction, so hopefully it's done correctly 🤞

Note that the initial commit failed with VM xcode-13.4.1 is invalid so I updated the xcode image to 14 which is the image that is in use in WCiOS.

Question: Does the .xcversion file need to be updated to 14.0 as well? I am guessing yes, but I am not familiar with the xcode version updates, so I'd appreciate some help.

Update

I had a few CI failures during publishing of the 4.1.0 version and ended up having to bump the version to 4.1.1.

@oguzkocer oguzkocer enabled auto-merge November 4, 2022 20:56
@oguzkocer oguzkocer requested a review from a team November 4, 2022 20:57
@oguzkocer oguzkocer changed the title Bump version to 4.1.0 Bump version to 4.1.1 Nov 5, 2022
Copy link
Contributor

@mokagio mokagio left a comment

Choose a reason for hiding this comment

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

This is my first release after the CHANGELOG.md introduction, so hopefully it's done correctly 🤞

LGTM! 👏 😄

Question: Does the .xcversion file need to be updated to 14.0 as well? I am guessing yes, but I am not familiar with the xcode version updates, so I'd appreciate some help.

This question comes at a very good time, as @AliSoftware suggested automation changes to fix an issue and overall improved the whole process in WooCommerce iOS.

If that's okay with you, I'll take this from here. I've suggested some minor changes in the Woo setup and I'd be happy to replicated the setup we'll land with from there in this repo (I'm also actively working on this repo, so it's no extra effort for me).

## 4.1.0-beta.1 [Unreleased]
## 4.2.0 [Unreleased]
Copy link
Contributor

Choose a reason for hiding this comment

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

The following is out of scope from this PR, because it correctly update the code based on its existing state, and also a big nitpick.

IMHO, this header should always stay "Unreleased" because it's up to the release manager (eventually the automation) to parse what went into the changelog since the latest release and decide what number to use based on the kind of changes.

I appreciate the idea of suggesting a new version number but I feel it would be neater if the header for unreleased code stayed fixed.

I might open a PR later on to update the template to make this clearer and we can discuss then.

Copy link
Contributor

Choose a reason for hiding this comment

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

Agreed. Predicted next version number will vary as new items will get added to the unreleased section, which is why we don't include a version number in it until we actually do the next release and decide on it based on content of the section and semver rules

@oguzkocer oguzkocer merged commit f6be0c8 into trunk Nov 7, 2022
@oguzkocer oguzkocer deleted the release/4.1.0 branch November 7, 2022 03: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.

3 participants