Skip to content

fix(ci): release packages that failed to publish due to invalid changeset flags - #2051

Merged
ArtieReus merged 1 commit into
mainfrom
artie-adds-changeset-to-publish
Oct 6, 2026
Merged

ArtieReus merged 1 commit into
mainfrom
artie-adds-changeset-to-publish

Conversation

@ArtieReus

Copy link
Copy Markdown
Collaborator

Summary

PR #2000 bumped versions for 14 packages, but they failed to publish to npm due to invalid flags in the release script. The fix for the invalid flags has already been merged to main, but the packages still need to be published.

This PR adds a patch changeset for all 14 affected packages to ensure they will be included in the next Version Packages PR and properly published to npm.

Changes Made

  • Created a patch changeset for all packages that were version bumped but failed to publish in PR publish(npm): automate Package Versioning and Publishing with Changesets #2000:
    • @cloudoperators/greenhouse-auth-provider
    • @cloudoperators/juno-app-doop
    • @cloudoperators/juno-app-greenhouse
    • @cloudoperators/juno-app-heureka
    • @cloudoperators/juno-app-supernova
    • @cloudoperators/juno-app-template
    • @cloudoperators/juno-communicator
    • @cloudoperators/juno-config
    • @cloudoperators/juno-k8s-client
    • @cloudoperators/juno-messages-provider
    • @cloudoperators/juno-oauth
    • @cloudoperators/juno-package-template
    • @cloudoperators/juno-ui-components
    • @cloudoperators/juno-url-state-provider

Related Issues

Screenshots (if applicable)

N/A - Changeset only

Testing Instructions

  1. Verify the changeset is recognized:
    pnpm changeset status
  2. Merge this PR and verify that:
    • A new Version Packages PR is created with patch bumps for all 14 packages
    • When that PR is merged, the publish workflow runs successfully and packages are published to npm

Checklist

  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have made corresponding changes to the documentation (if applicable).
  • My changes generate no new warnings or errors.
  • I have created a changeset for my changes.

Note: This PR only adds a changeset to trigger a new publish attempt for packages that failed previously. Tests are not applicable.

PR Manifesto

Review the PR Manifesto for best practises.

…eset flags

Signed-off-by: Arturo Reuschenbach Puncernau <reuschenbach@gmail.com>
@ArtieReus ArtieReus self-assigned this Oct 6, 2026
Copilot AI balanced review requested due to automatic review settings October 6, 2026 09:41
@ArtieReus
ArtieReus requested a review from a team as a code owner October 6, 2026 09:41
@changeset-bot

changeset-bot Bot commented Oct 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 9542a7f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 14 packages
Name Type
@cloudoperators/greenhouse-auth-provider Patch
@cloudoperators/juno-app-doop Patch
@cloudoperators/juno-app-greenhouse Patch
@cloudoperators/juno-app-heureka Patch
@cloudoperators/juno-app-supernova Patch
@cloudoperators/juno-app-template Patch
@cloudoperators/juno-communicator Patch
@cloudoperators/juno-config Patch
@cloudoperators/juno-k8s-client Patch
@cloudoperators/juno-messages-provider Patch
@cloudoperators/juno-oauth Patch
@cloudoperators/juno-package-template Patch
@cloudoperators/juno-ui-components Patch
@cloudoperators/juno-url-state-provider Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟡 Changes recommended

Seven listed packages are private and cannot be published under the current Changesets configuration.

Review effort: Balanced
Findings: 2 Medium severity

Open (2)
What changed in this PR

Adds a Changesets patch release to retry npm publication after the prior workflow failure.

Changes:

  • Schedules patch bumps for 14 packages.
  • Documents the failed publication retry.
File Description
.changeset/​fix-release-publish-flags.md Defines packages for the retry release.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .changeset/fix-release-publish-flags.md
Comment thread .changeset/fix-release-publish-flags.md
@ArtieReus
ArtieReus merged commit 8e22aa1 into main Oct 6, 2026
25 checks passed
@ArtieReus
ArtieReus deleted the artie-adds-changeset-to-publish branch October 6, 2026 09:46
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-06 09:46 UTC

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.

4 participants