v0.0.14

updated documentation for setting up sam-config repo

v0.0.13

updated some wording config script puts in toml file

v0.0.12

updated config.py to validate CommaDelimited parameters

v0.0.11

updated delete.py

v0.0.10

updated atlantis library for DefaultsLoader to fix tag import issue f…

v0.0.9

updated example in defaults.json

v0.0.8

updated doc

v0.0.7

Mostly stable. Still in Beta.

I'm going to go into a little more detail than usual.

• update.py (v0.1.5/2025-06-10): Fixed issue where the downloaded release zip file does not contain the v in front of the version number even if the release tag in GitHub has the v. This irregularity lies in GitHub and is a weird quirk that according to my conversation with GitHub Copilot is "undocumented but reproducible." This is even experienced when downloading a zip directly from the release page. The link will point to <url>/v0.0.6.zip, but the downloaded file will be <repo-name>-0.0.6.zip with files extracted to <repo-name>-0.0.6.zip.
• For the fix, GitHub Copilot recommended that instead of constructing the path beforehand, look inside the zip file and see what the actual path is. This should hopefully fix any future issue.

Below is GitHub Copilot's explanation. (Note: it says "This is a GitHub quirk for repositories with a dash (-) in the tag name" but there isn't a dash in the tag name, so there is still some inconsistencies as to why this happens.) However, I provide this information because:

1. GitHub Copilot admitted I was right :)
2. "This is not documented by GitHub, but is reproducible and widely observed." (so there could still be other quirks that need to be accounted for in the future)

From GitHub Copilot

Thank you for the detailed info and the direct observation.

You are correct: the downloaded file is named

atlantis-cfn-configuration-repo-for-serverless-deployments-0.0.6.zip

even though the tag is v0.0.6.

Why does this happen?

This is a GitHub quirk for repositories with a dash (-) in the tag name.

GitHub strips the leading v from the zip file and folder name if the tag is in the format vX.Y.Z.

• The actual tag in the repo is still v0.0.6.
• The zip file and extracted folder are named as if the tag is 0.0.6.

This is not documented by GitHub, but is reproducible and widely observed.

What does this mean for your code?

Your code currently does:

zipped_dir = f"{repo}-{tag}/"

If tag is v0.0.6, but the extracted folder is atlantis-cfn-configuration-repo-for-serverless-deployments-0.0.6/, your code will not find the right directory.

Summary

• GitHub sometimes strips the leading v from zip/folder names for tags like v0.0.6.
• Adjust your code to check for both possibilities.

v0.0.6

Mostly stable. Still in Beta.

• Fixed issue in update.py where if the AWS session token required a refresh, it would skip the requested pull

v0.0.5

Mostly stable. Still in Beta.

• Fixed issue where update.py was not pulling the latest changes from the organization's SAM config repository.
• Fixed issue where CodeCommit and Repository tags are being erroneously added to the tag prompts for the user even though they are automatically managed.