Skip to content

Fix Docker image tag: use v3.1.13 (latest available on Docker Hub) - #102

Merged
danenbm merged 1 commit into
mainfrom
danenbm/fix-docker-build
Apr 22, 2026
Merged

Fix Docker image tag: use v3.1.13 (latest available on Docker Hub)#102
danenbm merged 1 commit into
mainfrom
danenbm/fix-docker-build

Conversation

@danenbm

@danenbm danenbm commented Apr 22, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@coderabbitai

coderabbitai Bot commented Apr 22, 2026

Copy link
Copy Markdown

Summary by CodeRabbit

  • Chores
    • Updated Solana version from v3.1.14 to v3.1.13 across CI/CD pipelines and Docker builds.

Walkthrough

The Solana version referenced in GitHub workflows and Docker configuration was downgraded from v3.1.14 to v3.1.13. This affects the stable Solana release version used during CI/CD operations and Docker image builds.

Changes

Cohort / File(s) Summary
Workflow Configuration
.github/workflows/release.yml, .github/workflows/test.yml
Downgraded SOLANA_VERSION_STABLE environment variable from v3.1.14 to v3.1.13.
Docker Configuration
Solana.Dockerfile
Downgraded base image version by pinning SOLANA_VERSION build argument from v3.1.14 to v3.1.13.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request description is missing entirely; no description was added by the author, violating the template's expectation for a good description explaining the PR purpose. Add a description explaining why the Docker image tag was downgraded to v3.1.13, any related issues or breaking changes, and impact on the build or release process.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: updating the Docker image tag from v3.1.14 to v3.1.13 with context about Docker Hub availability.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch danenbm/fix-docker-build

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai 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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/release.yml (1)

6-10: 🧹 Nitpick | 🔵 Trivial

Consider a single source of truth for SOLANA_VERSION_STABLE.

The same version is now maintained in multiple files; moving it to a repo-level Actions variable (or shared workflow input) would reduce drift risk on future bumps.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/release.yml around lines 6 - 10, Extract the
SOLANA_VERSION_STABLE value into a single repo-level Actions variable (e.g., as
a workflow_call input or in .github/workflows/variables.yml) and replace the
hard-coded SOLANA_VERSION_STABLE entry in the release workflow with a reference
to that shared variable; update any other workflows that currently repeat
SOLANA_VERSION_STABLE to consume the new centralized variable so future bumps
require changing only the one source.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In @.github/workflows/release.yml:
- Around line 6-10: Extract the SOLANA_VERSION_STABLE value into a single
repo-level Actions variable (e.g., as a workflow_call input or in
.github/workflows/variables.yml) and replace the hard-coded
SOLANA_VERSION_STABLE entry in the release workflow with a reference to that
shared variable; update any other workflows that currently repeat
SOLANA_VERSION_STABLE to consume the new centralized variable so future bumps
require changing only the one source.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 416799a0-7cee-44d9-8647-3224538ada91

📥 Commits

Reviewing files that changed from the base of the PR and between 3d701a2 and e3ce017.

📒 Files selected for processing (3)
  • .github/workflows/release.yml
  • .github/workflows/test.yml
  • Solana.Dockerfile

@danenbm
danenbm merged commit 3b3b60c into main Apr 22, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants