Skip to content

docs: document CalVer transition across AWS, Snowflake, and Azure docs #494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
HarshCasper wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: document CalVer transition across AWS, Snowflake, and Azure docs #494

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1eeecb2
docs: document CalVer transition across AWS, Snowflake, and Azure docs
HarshCasper Mar 16, 2026
889e1d7
Apply suggestions from code review
quetzalliwrites Mar 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/content/docs/aws/capabilities/config/docker-images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,10 @@ The [BigData image](https://hub.docker.com/r/localstack/bigdata/tags), which sta

## Image tags

We use tags for versions with significant features, enhancements, or bug fixes - following [semantic versioning](https://semver.org).
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.14.0` use [semantic versioning](https://semver.org).
To ensure that we move quickly and steadily, we run nightly builds, where all our updates are available on the `latest` tag of LocalStack's Docker image.
We intend to announce more significant features and enhancements during major & minor releases.
We occasionally create patch releases for minor bug fixes and enhancements, to ensure that we can deliver changes quickly while not breaking your existing workflows (in case you prefer not to use `latest`).
Expand Down
10 changes: 7 additions & 3 deletions src/content/docs/aws/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ pagefind: false
Browse release notes for official LocalStack major and minor releases since LocalStack v1.0.0.
If you are looking for information about nightly releases, preview features, or experimental features, pull the [latest Docker image](https://hub.docker.com/r/localstack/localstack).

Our changelog is updated with every release.
Our changelog is updated with every release.

Updates that affect only LocalStack Web Application or features in preview or limited release may not be reflected.

Expand All @@ -26,8 +26,12 @@ Disclaimer: Features under development (i.e., labelled as preview/beta, experime

## Official Releases

LocalStack follows [Semantic Versioning](https://semver.org/) except for [AWS parity](https://localstack.cloud/blog/2022-08-04-parity-explained) fixes,
which can be released as patch version because we are committed to make LocalStack behave the same way AWS does.
Starting with the end-of-March 2026 release, LocalStack for AWS follows
[calendar versioning](https://calver.org/) using the `YYYY.MM.patch` format.
For example, `2026.03.0` is the initial March 2026 release and patch releases in the same month increment
the last segment (`2026.03.1`, `2026.03.2`, and so on).

Releases up to and including `v4.14.0` continue to use [Semantic Versioning](https://semver.org/).

| Version | Release Date | Release Notes |
|-----------|--------------------|----------------------------------------------------------------------------------------------------|
Expand Down
14 changes: 5 additions & 9 deletions src/content/docs/aws/getting-started/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,19 +82,15 @@ These tags have different semantics and will be updated on different occasions:
It will be updated with every release of LocalStack.
- This also entails major releases, which means that this tag can contain breaking changes.
- This tag should be used if you want to stay up-to-date with releases, but don't necessarily need the latest and greatest changes right away.
- `<major>` (e.g. `3`)
- These tags can be used to refer to the latest release of a specific major release.
It will be updated with every minor and patch release within this major release.
- This tag should be used if you want to avoid any potential breaking changes.
- `<major>.<minor>` (e.g. `3.0`)
- These tags can be used to refer to the latest release of a specific minor release.
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`)
Copy link
Member

@silv-io silv-io Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Collaborator

@quetzalliwrites quetzalliwrites Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @silv-io can you please do a commit suggestion for this one? I genuinely am not following what you want to change :)

Copy link
Member

@silv-io silv-io Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added it down below 👍🏼

Copy link
Member

@silv-io silv-io Mar 20, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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`)

- These tags can be used if you want to use a very specific release.
It will not be updated.
- This tag can be used if you really want to avoid any changes to the image (not even minimal bug fixes).

Starting with the end-of-March 2026 release, LocalStack follows [calendar versioning](https://calver.org/) for official releases.

For releases up to and including `v4.14.0`, tags follow Semantic Versioning.

### How can I access LocalStack from an alternative computer?

You can access LocalStack from an alternative computer, by exposing port `4566` to the public network interface (`0.0.0.0` instead of `127.0.0.1`) in your `docker-compose.yml` configuration.
Expand Down
4 changes: 4 additions & 0 deletions src/content/docs/azure/changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@ template: doc

This changelog tracks updates to LocalStack for Azure support, including new services, enhancements, and compatibility fixes.

Starting with the end-of-March 2026 release, LocalStack for Azure follows
[calendar versioning](https://calver.org/) in the `YYYY.MM.patch` format.
For example, `2026.03.0` is the initial March 2026 release.

LocalStack for Azure 0.1.0 supports the following services:

- [Azure API Management](https://azure.microsoft.com/en-us/products/api-management/)
Expand Down
4 changes: 4 additions & 0 deletions src/content/docs/azure/getting-started/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,3 +78,7 @@ $ docker-compose up

To update the Azure Docker container, pull the latest image and restart the container.
The `latest` tag is the nightly build of the Azure Docker image.

Starting with the end-of-March 2026 release, versioned Azure image tags follow
[calendar versioning](https://calver.org/) in the `YYYY.MM.patch` format (for example, `2026.03.0`).
Refer to the available [tags on Docker Hub](https://hub.docker.com/r/localstack/localstack-azure-alpha/tags) for the latest releases.
4 changes: 4 additions & 0 deletions src/content/docs/snowflake/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ editUrl: false

The LocalStack for Snowflake changelog tracks updates to LocalStack’s Snowflake support, including new features, enhancements, and compatibility fixes. Stay up to date on changes across official versioned releases of LocalStack’s Snowflake support.

Starting with the end-of-March 2026 release, LocalStack for Snowflake follows
[calendar versioning](https://calver.org/) in the `YYYY.MM.patch` format.
For example, `2026.03.0` is the initial March 2026 release.

### 1.7.0
- Add support for `OBJECT_AGG`, `QUERY_HISTORY_BY_USER`, `BOOLAND_AGG`, `BOOLOR_AGG`, `APPROX_PERCENTILE`, `LIKE`, `ILIKE`, and math functions
- Add support for date arithmetics
Expand Down
3 changes: 3 additions & 0 deletions src/content/docs/snowflake/getting-started/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,9 @@ If you only want to update the Snowflake image manually (e.g. to pick up a recen
docker pull localstack/snowflake:latest
```

Starting with the end-of-March 2026 release, versioned Snowflake image tags follow
[calendar versioning](https://calver.org/) in the `YYYY.MM.patch` format (for example, `2026.03.0`).
Refer to the available [tags on Docker Hub](https://hub.docker.com/r/localstack/snowflake/tags) for the latest releases.

## Alternatives

Expand Down