Skip to content

Conversation

@iangmaia
Copy link
Contributor

@iangmaia iangmaia commented Oct 7, 2025

Follow-up to AINFRA-1359

Description

This PR uses the 13.5.1 release-toolkit version that fixes the action update_assigned_milestone to work with fine-grained GitHub tokens (see PR wordpress-mobile/release-toolkit#663).

@iangmaia iangmaia self-assigned this Oct 7, 2025
@iangmaia iangmaia added the category: tooling Anything that involves building & maintaining the project, including scripts, `Fastfile`, etc. label Oct 7, 2025
@iangmaia iangmaia added this to the 23.5 milestone Oct 7, 2025
Gemfile Outdated
Comment on lines 12 to 14
# The '>= 13.5.1' after '~> 13.5' ensures that we resolve to any version compatible with 13.5 starting from 13.5.1
# We need 13.5.1 because of a fix in fetching issues / PRs with a fine-grained GitHub token
gem 'fastlane-plugin-wpmreleasetoolkit', '~> 13.5', '>= 13.5.1'
Copy link
Contributor

Choose a reason for hiding this comment

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

💄 This is fine, though tbh ~> 13.5 could also have been enough as long as you made sure to re-run bundle update fastlane-plugin-wpmreleasetoolkit once 13.5.1 was deployed so that the dependency resolution would discover it and pick it.
(As long as the Gemfile.lock lockfile is on a version that is >=13.5.1 after you do such update, there's no way it would risk regressing to 13.5.0 later on)

But I don't mind being explicit in the Gemfile even if the Gemfile.lock would have already resolved it to 13.5.1, both are valid anyway 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm yeah I was basically following what the Gemfile on iOS had, I've seen this pattern in a few of our Gemfiles. Tbh I'd prefer not to be redundant... and these comments are bound to be out of date / not relevant anyway while dependencies are getting updated (like the previous iOS one did).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated on acf8e1b, favoring a clean-up.

iangmaia added a commit that referenced this pull request Oct 8, 2025
iangmaia added a commit to woocommerce/woocommerce-ios that referenced this pull request Oct 8, 2025
iangmaia added a commit to woocommerce/woocommerce-ios that referenced this pull request Oct 8, 2025
@iangmaia iangmaia force-pushed the iangmaia/fix-release-toolkit-milestone-moving branch from acf8e1b to 90040b4 Compare October 8, 2025 15:44
@iangmaia iangmaia enabled auto-merge October 8, 2025 15:46
@iangmaia iangmaia merged commit eb570e9 into trunk Oct 8, 2025
13 of 15 checks passed
@iangmaia iangmaia deleted the iangmaia/fix-release-toolkit-milestone-moving branch October 8, 2025 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

category: tooling Anything that involves building & maintaining the project, including scripts, `Fastfile`, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants