Skip to content

wp/6.5: Fetch the release tags before Lerna looks for changed packages - #883

Open
desrosj wants to merge 1 commit into
fix-actions-wp-6.5-npm-publish-wp-onlyfrom
fix-actions-wp-6.5-npm-publish-fetch-tags
Open

desrosj wants to merge 1 commit into
fix-actions-wp-6.5-npm-publish-wp-onlyfrom
fix-actions-wp-6.5-npm-publish-fetch-tags

Conversation

@desrosj

@desrosj desrosj commented Nov 2, 2026

Copy link
Copy Markdown
Owner

What?

Adds a step that fetches wp/6.5 again inside the publish checkout before Lerna runs, which brings in the release tags on its history.

Commit: a043daa

Why?

actions/checkout always fetches with --no-tags unless fetch-tags: true is set. fetch-depth: 999 brings in the history but none of the tags, so Lerna cannot find the previous release, logs Assuming all packages changed, and bumps and publishes every public package. A plain git fetch follows the tags on the fetched history; fetch-tags: true would fetch all of the repository's tags at depth 999 instead.

Testing Instructions

  • With the tags on this branch, lerna changed diffs against @wordpress/block-library@8.28.13 and lists 24 packages.
  • A checkout made the way actions/checkout makes it (--no-tags --depth=999) has no tags, and Lerna then lists every public package. Running the new fetch afterwards brings the baseline tag back. Tested on wp/6.4, where that is 93 packages without the tags and 23 with them.
  • actionlint passes.

🤖 Generated with Claude Code

@desrosj
desrosj added this pull request to stack #886 November 2, 2026 19:41
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

🤖 PR meta 🤖

🏷️ Labels

This pull request needs exactly one label indicating its type, and has 0.

  • Required: any label starting with [Type].
  • Found: none.

Read more about Type labels in Gutenberg. If you cannot add labels yourself, a reviewer can do it for you.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

This branch has not been deployed

No deployments
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.

1 participant