fix(release): correct version for 4.61.0#24156
Conversation
Signed-off-by: Chaimaa ZEGOUMOU <chaimaa.zegoumou@docker.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
the
area/desktop
![docker-agent[bot]](https://avatars.githubusercontent.com/in/2787757?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Summary
Found one issue that should be verified: the version number was updated from 4.60.1 to 4.61.0, but the build_path remains unchanged at "/219004/". Typically, when a version is incremented, the build path should also be updated to reference the new release's build artifacts.
This could be correct if the build artifacts for 4.61.0 are actually stored at this path, but it's worth double-checking to ensure the version and build path are properly synchronized.
| {{< release-date date="2026-02-16" >}} | ||
|
|
||
| {{< desktop-install-v2 all=true win_arm_release="Early Access" version="4.60.1" build_path="/219004/" >}} | ||
| {{< desktop-install-v2 all=true win_arm_release="Early Access" version="4.61.0" build_path="/219004/" >}} |
There was a problem hiding this comment.
Version and Build Path Synchronization
The version was updated from 4.60.1 to 4.61.0, but the build_path parameter remains at "/219004/". Typically, when a version number is incremented, the build path (which points to release artifacts) should also be updated to reference the new release's build directory.
Please verify:
- Is
/219004/the correct build path for version 4.61.0? - Should this be updated to a different build path corresponding to the 4.61.0 release?
If the build artifacts for 4.61.0 are indeed at this path, then this is correct. Otherwise, the build_path should be updated to match the new version.
2 participants
Description
Related issues or tickets
Reviews