Skip to content

Commit 05f7860

Browse files
docs: update container version references to v1.5.0
Update all pinned version examples from v1.3.2 to v1.5.0 across container docs, GitHub template, and GitLab template pages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent bbcec6c commit 05f7860

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

content/docs/container/_index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The dev-toolchain image is hosted on GitHub Container Registry (GHCR):
1616
docker pull ghcr.io/devrail-dev/dev-toolchain:v1
1717

1818
# Pull a specific version (for reproducible builds)
19-
docker pull ghcr.io/devrail-dev/dev-toolchain:v1.3.2
19+
docker pull ghcr.io/devrail-dev/dev-toolchain:v1.5.0
2020
```
2121

2222
## How It Works with the Makefile
@@ -101,25 +101,25 @@ For projects requiring reproducible builds, pin to an exact semver tag:
101101

102102
```makefile
103103
# Pin to an exact version for reproducibility
104-
DEVRAIL_IMAGE ?= ghcr.io/devrail-dev/dev-toolchain:v1.3.2
104+
DEVRAIL_IMAGE ?= ghcr.io/devrail-dev/dev-toolchain:v1.5.0
105105
```
106106

107107
### Tagging Strategy
108108

109109
| Tag | Example | Behavior |
110110
|---|---|---|
111111
| Major floating | `v1` | Updated on every release; non-breaking updates propagate automatically |
112-
| Exact semver | `v1.3.2` | Immutable; never updated after publication |
112+
| Exact semver | `v1.5.0` | Immutable; never updated after publication |
113113

114-
Weekly builds publish both an exact semver tag (e.g., `v1.3.2`) and update the floating major tag (`v1`). Breaking changes bump the major version.
114+
Weekly builds publish both an exact semver tag (e.g., `v1.5.0`) and update the floating major tag (`v1`). Breaking changes bump the major version.
115115

116116
### Upgrading
117117

118118
To upgrade to a new exact version:
119119

120120
```makefile
121121
# Update the version in your Makefile
122-
DEVRAIL_IMAGE ?= ghcr.io/devrail-dev/dev-toolchain:v1.4.0
122+
DEVRAIL_IMAGE ?= ghcr.io/devrail-dev/dev-toolchain:v1.5.0
123123
```
124124

125125
If you use the floating `v1` tag, upgrades happen automatically when the container image is re-pulled.

content/docs/templates/github.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ To pin a specific container version:
128128

129129
```makefile
130130
# In your Makefile, override the default image
131-
DEVRAIL_IMAGE ?= ghcr.io/devrail-dev/dev-toolchain:v1.3.2
131+
DEVRAIL_IMAGE ?= ghcr.io/devrail-dev/dev-toolchain:v1.5.0
132132
```
133133

134134
### Adjusting CI Triggers

content/docs/templates/gitlab.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ Override the container image in `.gitlab-ci.yml`:
164164

165165
```yaml
166166
# Pin to a specific version
167-
image: ghcr.io/devrail-dev/dev-toolchain:v1.3.2
167+
image: ghcr.io/devrail-dev/dev-toolchain:v1.5.0
168168
```
169169

170170
Also update the `DEVRAIL_IMAGE` variable in your `Makefile` for local development consistency.

0 commit comments

Comments
 (0)