fix(deps): release widespread dependency bumps across root, functions & infra - #620
Merged
Conversation
… & infra Empty commit to make the dependency bumps from #617 releasable. #617 landed production dependency upgrades (next, urql/@urql/*, @nhost/nhost-js, graphql, gql.tada, react-hook-form, lexical, recharts, @google/genai) plus nhost infra bumps (hasura v2.49.4-ce, postgres 18.4-20260610-1, storage 0.15.0), but was committed as `chore(deps)`. release-please treats `chore` as a hidden, non-releasable type, so it cut no release and the `Deploy Prod` step (gated on release_created) was skipped — leaving those changes sitting on main, unreleased. Per this repo's Renovate convention, production dependency updates use `fix(deps)` (releasable) while devDeps/tooling use `chore(deps)`. This commit applies the correct type so release-please cuts a patch release and promotes main to production. No file changes — see #617 for the actual diff and its verification. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Up to standards ✅🟢 Issues
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Empty commit to make the dependency bumps from #617 releasable. No file changes — see #617 for the actual diff and verification.
Why
#617 is merged to
main, but it never deployed to production. It was committed aschore(deps), and release-please treatschoreas a hidden, non-releasable type. So it cut no release,release_createdstayed false, and the gated steps were skipped:Those upgrades are sitting on
main, unreleased — including production dependencies (next,urql/@urql/*,@nhost/nhost-js,graphql,gql.tada,react-hook-form,lexical,recharts,@google/genai) and the nhost infra bumps (hasurav2.49.4-ce, postgres18.4-20260610-1, storage0.15.0).Per this repo's Renovate convention, production dependency updates use
fix(deps)(releasable) while devDeps/tooling usechore(deps)— e.g. #619fix(deps): …biome, #618fix(deps): …motionvs #587chore(deps): …pnpm, #570chore(deps): …node. #617 should have beenfix(deps); this commit applies the correct type.What happens on merge
release-please cuts a patch release (
0.58.3) covering everything onmain, including #617. Merging that release PR setsrelease_created, which runsDeploy Prod(fast-forwardmain→production).Reviewer note
nhost config validateand their image tags were confirmed to exist upstream, but the full stack was never booted to prove the containers pull and start. If you want a smoke-test before those hit prod, hold this PR and runnhost uplocally first.🤖 Generated with Claude Code