Skip to content

chore: release auth0-nuxt v1.2.0 - #61

Closed
gyaneshgouraw-okta wants to merge 1 commit into
mainfrom
release/auth0-nuxt-v1.2.0
Closed

chore: release auth0-nuxt v1.2.0#61
gyaneshgouraw-okta wants to merge 1 commit into
mainfrom
release/auth0-nuxt-v1.2.0

Conversation

@gyaneshgouraw-okta

Copy link
Copy Markdown
Contributor

Added

Fixed

Full Changelog

@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (2)
  • release
  • chore: release

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 116ddaf8-b889-4e8b-b195-d792636bf4a2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gyaneshgouraw-okta

Copy link
Copy Markdown
Contributor Author

Not for merge. This PR exists only so the release workflow could find a PR with the expected head branch: release/auth0-nuxt-v1.2.0.

Background

The original release PR #60 was created from release/v1.2.0, missing the auth0-nuxt- package prefix expected by .github/actions/get-release-notes.

As a result, the PR lookup returned no results and the workflow failed on pulls[0].body ([run 32473144935]).

The version bump had already merged to main, but the tag, npm publish, and GitHub release had not been created.
auth0-nuxt-v1.2.0 is now tagged and published, so this PR can be closed without merging.

Follow-ups

  • Add .shiprc with packageLabel: "auth0-nuxt" so release branch names are generated correctly.
  • Guard the empty pulls case so the workflow provides a clear error message.

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