docs: document CalVer transition across AWS, Snowflake, and Azure docs#494
Open
HarshCasper wants to merge 2 commits intomainfrom
Open
docs: document CalVer transition across AWS, Snowflake, and Azure docs#494HarshCasper wants to merge 2 commits intomainfrom
HarshCasper wants to merge 2 commits intomainfrom
Conversation
HarshCasper
requested review from
quetzalliwrites and
remotesynth
as code owners
HarshCasper
requested review from
alexrashed,
bblommers,
hovaesco,
mmaureenliu,
paolosalvatori and
silv-io
Deploying localstack-docs with
|
| Latest commit: |
889e1d7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://816b3b29.localstack-docs.pages.dev |
| Branch Preview URL: | https://harshmishra-doc-52.localstack-docs.pages.dev |
remotesynth
approved these changes
Mar 16, 2026
hovaesco
approved these changes
Mar 17, 2026
quetzalliwrites
approved these changes
Mar 17, 2026
Collaborator
quetzalliwrites
left a comment
quetzalliwrites
left a comment
There was a problem hiding this comment.
tyvm @HarshCasper ❤️ !!
Collaborator
|
@silv-io where are we good to merge this one? do we wait till the 23rd? |
silv-io
reviewed
Mar 17, 2026
Member
silv-io
left a comment
silv-io
left a comment
There was a problem hiding this comment.
some minor nitpicks :) after they're resolved I think we'll be ready to go.
| Starting with the end-of-March 2026 release, LocalStack version tags follow | ||
| [calendar versioning](https://calver.org/) in the `YYYY.MM.patch` format (for example, `2026.03.0`). | ||
|
|
||
| Releases up to and including `v4.13.0` use [semantic versioning](https://semver.org). |
Member
There was a problem hiding this comment.
will keep in mind for the future :D
| It will be updated with every patch release within this minor release. | ||
| - This tag can be used if you want to avoid any bigger changes, like new features, but still want to update to the latest bugfix release. | ||
| - `<major>.<minor>.<patch>` (e.g. `3.0.2`) | ||
| - `<YYYY.MM.patch>` (e.g. `2026.03.0`) |
Member
There was a problem hiding this comment.
nit: you'll still be able to do 2026 and 2026.03 as tags! :)
the yearly one IDK how useful it is, but the monthly one can be nice if you want to accept any patch change
Collaborator
There was a problem hiding this comment.
hey @silv-io can you please do a commit suggestion for this one? I genuinely am not following what you want to change :)
Co-authored-by: Quetzalli <alejandra.olvera.novack@gmail.com>
bblommers
approved these changes
Mar 20, 2026
silv-io
reviewed
Mar 20, 2026
| It will be updated with every patch release within this minor release. | ||
| - This tag can be used if you want to avoid any bigger changes, like new features, but still want to update to the latest bugfix release. | ||
| - `<major>.<minor>.<patch>` (e.g. `3.0.2`) | ||
| - `<YYYY.MM.patch>` (e.g. `2026.03.0`) |
Member
There was a problem hiding this comment.
Suggested change
| - `<YYYY.MM.patch>` (e.g. `2026.03.0`) | |
| - `<YYYY.MM>` (e.g., `2026.03`) | |
| - These tags can be used to refer to the latest release of a month. It will be updated with every patch release within this month. | |
| - This tag can be used if you want to avoid any bigger changes, like new features, but still want to update to the latest bugfix release. | |
| - `<YYYY.MM.patch>` (e.g., `2026.03.0`) |
silv-io
approved these changes
Mar 20, 2026
Member
silv-io
left a comment
silv-io
left a comment
There was a problem hiding this comment.
After my suggestion is in, we're ready to merge 👍🏼
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
6 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.
Fixes DOC-52