Repository navigation
fix(deps): refresh supported graph and packaged action - #369
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Every action invocation loads this file through action.yml, but at byte 393216 (this line) the bundle changes from JavaScript to non-UTF-8 binary data. Running node dist/index.js or node --check dist/index.js as an ES module raises a SyntaxError here, so the action fails before reading inputs or contacting Jira; replace this artifact with the complete Rollup output and regenerate its source map.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Refresh the current Yarn 1.22.22 graph within the existing manifest ranges and rebuild both committed action artifacts. This resolves the stale transitive security patches without changing the Jira API major or adding overrides.
Verification: frozen reinstall, 22 unit tests, Biome lint and Rollup build pass locally on Node 24.19.0. Audit falls from 40 distinct advisories to four, with no runtime dependency advisory remaining in this audit. CI must verify frozen install, bundle parity and real Jira behavior on this head.
Remaining advisories are explicitly assessed:
No overrides added, audit errors suppressed, or workflows disabled. These residuals require reassessment when upstream supported dependency ranges change.