Skip to content

fix(deps): restore @forge/api as a direct dependency - #62

Merged
matthewelwell merged 1 commit into
mainfrom
investigate/forge-resolver-deploy-failure
Jun 30, 2026
Merged

fix(deps): restore @forge/api as a direct dependency#62
matthewelwell merged 1 commit into
mainfrom
investigate/forge-resolver-deploy-failure

Conversation

@matthewelwell

@matthewelwell matthewelwell commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Fixes the forge bundling failure that has been breaking deployments since #60.

@forge/api was previously satisfied as a transitive dependency of @forge/resolver@1.6.10. The bump to 1.8.0 in #60 dropped it, but there are direct imports in the code. This PR adds it back as a direct dependency.

🤖 Generated with Claude Code

@forge/api was previously pulled in as a transitive of @forge/resolver
1.6.10. Resolver 1.8.0 (#60) no longer depends on it, breaking the
forge deploy bundling step.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@matthewelwell
matthewelwell requested a review from a team as a code owner June 29, 2026 19:07
@matthewelwell
matthewelwell requested review from kyle-ssg and removed request for a team June 29, 2026 19:07

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request adds the @forge/api dependency (version 5.2.0) to the flagsmith-jira-app package, updating both package.json and package-lock.json with the new package and its transitive dependencies. There are no review comments, so I have no feedback to provide.

@matthewelwell
matthewelwell merged commit 064eaf0 into main Jun 30, 2026
3 checks passed
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.

3 participants