You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cli/CHANGELOG.md
+52-1Lines changed: 52 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,61 @@ To update your local cli scripts from GitHub repository:
12
12
- Refer to [TODO](../TODO.md) for upcoming BETA fixes and features.
13
13
- Report any issues not covered in TODO via the [Issues page in the GitHub repository](https://github.com/63Klabs/atlantis-cfn-configuration-repo-for-serverless-deployments/issues)
14
14
15
-
## v0.0.7 (2025-06-xx)
15
+
## v0.0.8 (2025-06-xx)
16
16
17
17
Upcoming
18
18
19
+
## v0.0.7 (2025-06-10)
20
+
21
+
Mostly stable. Still in Beta.
22
+
23
+
I'm going to go into a little more detail than usual.
24
+
25
+
- 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`.
26
+
- 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.
27
+
28
+
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:
29
+
30
+
1. GitHub Copilot admitted I was right :)
31
+
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)
32
+
33
+
### From GitHub Copilot
34
+
35
+
Thank you for the detailed info and the direct observation.
This is a GitHub quirk for repositories with a dash (`-`) in the tag name.
47
+
48
+
GitHub strips the leading `v` from the zip file and folder name **if the tag is in the format `vX.Y.Z`**.
49
+
50
+
- The actual tag in the repo is still `v0.0.6`.
51
+
- The zip file and extracted folder are named as if the tag is `0.0.6`.
52
+
53
+
**This is not documented by GitHub, but is reproducible and widely observed.**
54
+
55
+
#### What does this mean for your code?
56
+
57
+
Your code currently does:
58
+
59
+
```python
60
+
zipped_dir =f"{repo}-{tag}/"
61
+
```
62
+
63
+
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.
64
+
65
+
#### Summary
66
+
67
+
- GitHub sometimes strips the leading `v` from zip/folder names for tags like `v0.0.6`.
68
+
- Adjust your code to check for both possibilities.
0 commit comments