Skip to content

chore(main): release 10.0.4 - #1147

Merged
BethGriggs merged 1 commit into
mainfrom
release-please--branches--main--components--citgm
Oct 12, 2026
Merged

BethGriggs merged 1 commit into
mainfrom
release-please--branches--main--components--citgm

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

10.0.4 (2026-10-12)

Lookup Updates


This PR was generated with Release Please. See documentation.

@BethGriggs

BethGriggs commented Sep 28, 2026 •

Copy link
Copy Markdown
Member

Now 10.0.3 was released to test the new release process, I think we can use this release for a number of the lookup changes that we have planned/queued up.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--citgm branch 5 times, most recently from 8336003 to 2f18eaa Compare October 1, 2026 12:56
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--citgm branch 2 times, most recently from 53b337c to c29c294 Compare October 6, 2026 12:28
@MikeMcC399

MikeMcC399 commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

@BethGriggs

The new release process has changed the tag format. Whereas previously releases were tagged:
v10.0.2
v10.0.1
v10.0.0
etc.

the latest release was tagged citgm-v10.0.3. This is unusual and it makes https://github.com/nodejs/citgm/tags inconsistent.

Please check if you want to continue this way, or if you want to revert to the previous format.

For comparison, https://github.com/nodejs/corepack/releases also uses release-please and it doesn't include the name of the package / repo as a prefix to the tags it creates.

Edit: this is addressed in #1183 - I'll leave this comment visible though until it's been proved successful in the next release

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--citgm branch 4 times, most recently from 50abbe8 to b78f162 Compare October 7, 2026 13:33
@BethGriggs BethGriggs mentioned this pull request Oct 7, 2026
1 task done
@github-actions github-actions Bot changed the title chore(main): release citgm 10.0.4 chore(main): release 10.0.4 Oct 7, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--citgm branch 3 times, most recently from e5c8c48 to 9f6a1c1 Compare October 8, 2026 18:32
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--citgm branch from 9f6a1c1 to f577c5f Compare October 12, 2026 11:18
@codecov-commenter

codecov-commenter commented Oct 12, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.20%. Comparing base (eeb7a8b) to head (f577c5f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1147   +/-   ##
=======================================
  Coverage   96.20%   96.20%           
=======================================
  Files          29       29           
  Lines        2213     2213           
=======================================
  Hits         2129     2129           
  Misses         84       84           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@BethGriggs

Copy link
Copy Markdown
Member

I'm going to go ahead and trigger this release so the lookup changes are in effect for planned releases.

@BethGriggs
BethGriggs merged commit 37e1545 into main Oct 12, 2026
11 checks passed
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants