feat(module/deploy): CLI deploy verb — record version from code + deploy#39
Merged
Conversation
Add `mirrorstack module deploy`: the module's code is the source of truth.
Deploy reads the newest `Config.Versions` key out of main.go, records that
version (immutable snapshot + manifest) when it isn't recorded yet, then
points it at a Lambda invoke target — one developer verb, publish merged in.
- api: record_module_version / list_module_versions / set_module_deploy /
get_tunnel_manifest, with platform error-envelope surfacing.
- module_meta: parse + SemVer-rank the Versions map keys, promote a
`-dev` key in-place at deploy time.
- README + CHANGELOG captured as locale maps ({default, <tag>}), each read
off disk at the module root and version-section respectively.
- scaffold/template: reword publish→deploy; `-dev` refused under --yes.
Pairs with the api-platform module_deploys writer (already merged, #284).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
Adds
mirrorstack module deploy— the whole CLI deploy verb. The module'scode is the source of truth: deploy reads the newest
Config.Versionskey out of
main.go, records that version (immutable snapshot + livemanifest) when it isn't recorded yet, then points it at a Lambda invoke
target.
publishis merged intodeploy— one developer verb.Contents
record_module_version,list_module_versions,set_module_deploy,get_tunnel_manifest, each surfacing the platformerror-envelope (
version_exists,invoke_target_invalid,changelog_too_large,tunnel_offline, …).Versionsmap keys frommain.go, SemVer-rankthem, and promote a
-devkey in place at deploy time.{ "default": …, "<tag>": … }— README read off disk at the module root,CHANGELOG as the matching
## <version>section.-devversions refusedunder
--yes(CI) by convention.Why this is one clean PR
Collapses the old
feat/module-deploy-cmdstack (which had pre-monorepo-rebasedev-runner WIP commits and conflicted with
main) into a single coherentcommit off the current
main. The dev-runner / app-command / credentialschurn on the old stack was superseded by main's monorepo rebase and is dropped;
only the deploy verb remains. No merge commits, no leftover markers,
cargo build+cargo test(144) +cargo fmt --check+cargo clippyall green.Pairs with the api-platform
module_deployswriter already merged (#284).