Bump version to 0.0.195#467
Merged
Merged
Conversation
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.
Release bump after #466 (git auto-init on first push).
What's in 0.0.195
feat(git): auto-init a bare repo on first push to an empty path. Resolves Git HTTP backend: add an init primitive so pod paths can become git repos remotely #465. Net new code: 52 lines insrc/handlers/git.js(most of it JSDoc + safety contract documentation) + 6 tests intest/git-auto-init.test.js(the first test coverage of the git HTTP backend). Full test suite (876 tests) passes.Publish checklist
npm testgreenpackage.jsonbumped to0.0.195npm publishafter mergeNote on the lockfile
package-lock.jsonstill reads0.0.191— the same drift that's been carried for 3 prior releases. Not touching it here to match the existing JSS bump convention. Worth a separate cleanup PR if/when desired.