fix: correct csproj filename typo in release-please config#274
Merged
Tr00d merged 1 commit intoJul 14, 2026
Merged
Conversation
Tr00d
marked this pull request as ready for review
July 13, 2026 12:52
QuintinWillison
approved these changes
Jul 13, 2026
spydon
approved these changes
Jul 13, 2026
Tr00d
deleted the
guillaumefaas/sdk-1233-fix-release-please-config-typo-for-supabase-package
branch
July 14, 2026 07:52
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
3 participants
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.
Summary
A typo in
release-please-config.jsoncaused the version bump step to silentlytarget a non-existent file (
Supbase.csprojinstead ofSupabase.csproj).As a result, when v1.1.2 was released, the manifest and changelog were updated
correctly but
Supabase.csprojwas never patched — so no 1.1.2 package wasever published to NuGet. The GitHub release and the published package have been
out of sync since then.
What this changes
Corrects the filename in
extra-filesso subsequent releases patch the real.csproj. The 1.1.2 gap is accepted; the next release (1.2.0, given pendingfeat:commits) will be the first to tag and publish in lockstep.What this does not change
Nothing in the publish workflow, the manifest, or the
.csprojitself. This isa one-line config fix.