Repository navigation
chore: start sync-mongodb and sync-mysql at 0.0.1 - #51
Merged
Merged
Conversation
Both packages are being published by hand at 0.0.1 so that npm trusted publishers can be configured, the same seed as sync-engine and sync-postgres. The manifest baseline also matters: release-please reads 0.0.0 as "never released" and proposes 1.0.0 for a first release (see the open release PR), while from 0.0.1 the next release computes to 0.1.0.
 [Medium impact] This PR appears safe to merge. SummarySets
Reviews (2) · Last reviewed commit: "Merge branch 'main' into chore/seed-mong..." · Reviewed by Greptile |
gjtorikian
added a commit
that referenced
this pull request
Nov 6, 2026
The same seed as the other packages (#51): the first version is published by hand so the npm trusted publisher can be configured, and release-please reads 0.0.0 as never released and would propose 1.0.0, where from 0.0.1 the next release computes to 0.1.0.
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
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.
What
Sets
@workos/sync-mongodband@workos/sync-mysqlto 0.0.1 in theirpackage.jsonand in.release-please-manifest.json.Why
Both packages are being published by hand at 0.0.1 so npm trusted publishers can be configured, the same seed as sync-engine and sync-postgres got. The manifest baseline also matters: release-please reads
0.0.0as "never released" and proposes 1.0.0 for a first release (see #43), while from 0.0.1 the next release computes to 0.1.0 underbump-minor-pre-major.After this merges, release-please will regenerate #43 with 0.1.0 for both new packages.