Skip to content

Publish version after SnapStart config update during zappa update#1450

Merged
monkut merged 1 commit intomasterfrom
fix/1448-snapstart-requires-version-publish
Apr 6, 2026
Merged

Publish version after SnapStart config update during zappa update#1450
monkut merged 1 commit intomasterfrom
fix/1448-snapstart-requires-version-publish

Conversation

@monkut
Copy link
Copy Markdown
Collaborator

@monkut monkut commented Apr 6, 2026

Summary

Test plan

  • New test: test_snap_start_publishes_version_after_config_update — verifies publish_version is called when snap_start is enabled
  • New test: test_snap_start_disabled_does_not_publish_extra_version — verifies no extra publish when snap_start is disabled
  • New test: test_snap_start_updates_alb_alias_after_publish — verifies ALB alias is updated to point to the new version
  • All 156 existing tests pass

…1448)

During `zappa update`, the version was published before SnapStart was
enabled in the config. Since SnapStart only snapshots versions published
after enablement, the latest version never got a snapshot. Fix by
publishing an additional version after updating the configuration when
snap_start is enabled, and updating the ALB alias if present.
@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 74.651% (+0.04%) from 74.614%
when pulling 2b5698f on fix/1448-snapstart-requires-version-publish
into e0e65a2 on master.

@monkut monkut merged commit 7366118 into master Apr 6, 2026
7 checks passed
@monkut monkut deleted the fix/1448-snapstart-requires-version-publish branch April 6, 2026 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SnapStart requires version publish after config update, but zappa update publishes before enabling

3 participants