Skip to content

[CI] Upgrade project to Go 1.26.4#151

Open
KumarNirupam1 wants to merge 5 commits into
layer5io:masterfrom
KumarNirupam1:feature/update/go1.26.4
Open

[CI] Upgrade project to Go 1.26.4#151
KumarNirupam1 wants to merge 5 commits into
layer5io:masterfrom
KumarNirupam1:feature/update/go1.26.4

Conversation

@KumarNirupam1

@KumarNirupam1 KumarNirupam1 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Notes for Reviewers

This PR fixes #149

Changes

  1. Go 1.26.4 upgrade — Updates go.mod and .github/build/Makefile.core.mk from 1.24.5 to 1.26.4. CI workflows already use go-version-file: go.mod, so no workflow changes were required.

  2. academy-theme v0.4.17 — Bumps github.com/layer5io/academy-theme from v0.4.16 → v0.4.17 to fix a CI build failure.

Why the theme bump?

master includes content/content-formatting-examples/academy-theme/org-id.md, which uses the {{< org-id >}} shortcode. That shortcode was added in academy-theme v0.4.17 and is not present in v0.4.16.

Without the theme bump, make build-preview fails with:

Signed commits

  • Yes, I signed my commits.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request attempts to upgrade the Go version from 1.24.5 to 1.26.4 in both the Makefile and go.mod. However, Go 1.26.4 is not a released version, which will lead to build and CI pipeline failures. Both review comments correctly point out this issue and suggest reverting to a valid, stable Go version.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread go.mod
Comment thread .github/build/Makefile.core.mk
Fixes layer5io#149

Signed-off-by: Kumar Nirupam <kumar.nirupam24@gmail.com>
@KumarNirupam1 KumarNirupam1 force-pushed the feature/update/go1.26.4 branch from 948cc5d to 5e97ad8 Compare June 25, 2026 07:02
Required for org-id shortcode used in content formatting examples.
Fixes CI build failure.
Signed-off-by: Kumar Nirupam <kumar.nirupam24@gmail.com>

Signed-off-by: Kumar Nirupam <kumar.nirupam24@gmail.com>
@github-actions

Copy link
Copy Markdown

🚀 Preview deployment: https://layer5io.github.io/academy-example/pr-preview/pr-151/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

@KumarNirupam1

KumarNirupam1 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

@leecalcote @CodexRaunak the PR is ready to review

@leecalcote leecalcote left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Updates to workflows is missing.

Signed-off-by: Kumar Nirupam <kumar.nirupam24@gmail.com>
@KumarNirupam1

Copy link
Copy Markdown
Contributor Author

@leecalcote added Setup Go to build-and-release.yml using go-version-file: go.mod (same as the other workflows).

The preview/deploy workflows already read Go version from go.mod, so no changes needed there.

@KumarNirupam1 KumarNirupam1 requested a review from leecalcote June 25, 2026 18:30
Comment thread .github/workflows/build-and-release.yml
@KumarNirupam1 KumarNirupam1 requested a review from Sbragul26 June 26, 2026 03:24
@KumarNirupam1

Copy link
Copy Markdown
Contributor Author

@Sbragul26 Thanks for the review

you're right that make setup and make build don't call go directly.

Hugo still uses the Go toolchain behind the scenes for Hugo Modules (e.g. when resolving academy-theme during hugo: collected modules).

I added the Setup Go step here to align with build-and-preview-site.yml and build-and-deploy-site.yml, which already use go-version-file: go.mod, after lee's feedback that workflow updates were missing.

@Sbragul26

Copy link
Copy Markdown
Member

Should we also add a Setup Node step? This workflow uses npm, so it looks like this step is missing.

@KumarNirupam1

KumarNirupam1 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

ok so since this workflow uses npm through make setup
i'll add the Setup Node step here too, same as the other workflows. will push the update shortly.

Signed-off-by: Kumar Nirupam <kumar.nirupam24@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade project to go1.26.4

3 participants