chore: Need to create the workflow in main so it can be updated and run in v2 branch

[danielpanzella]

Summary by CodeRabbit

• Chores
  • Added a new manually-triggered CI workflow to publish internal container images. Users can specify an image tag when starting the workflow; it runs on the CI runner, checks out the repository and performs the release steps to prepare and push the specified image.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Adds a new GitHub Actions workflow file .github/workflows/internal-image-publish.yaml named "Internal Image Publish". It is manually triggerable via workflow_dispatch with a required image_tag input and defines a single Release job running on ubuntu-latest that checks out the repository with persist-credentials: false and fetch-depth: 0.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/internal-image-publish.yaml	New workflow Internal Image Publish triggered via workflow_dispatch with required image_tag input. Defines a single Release job on ubuntu-latest and includes an actions/checkout@v2 step configured with persist-credentials: false and fetch-depth: 0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 I stitched a workflow, neat and spry,

For images that reach the sky,
A manual nudge, a tag to share,
Checkout ready, runners prepare,
The rabbit hops — CI lights the way. 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: creating a new workflow in the main branch for future updates and execution in the v2 branch.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch danielpanzella/internal-image-publish-action

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/internal-image-publish.yaml:
- Line 17: The workflow uses an outdated action reference "actions/checkout@v2"
which pins Node 12 and will fail; update the checkout step to
"actions/checkout@v4" everywhere it appears in the workflow file (replace the
uses: value in the checkout step), commit the change, and verify any dependent
steps still work with the newer checkout action.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Update actions/checkout from v2 to v4.

actions/checkout@v2 uses Node.js 12, which is no longer supported on GitHub Actions runners and will fail. This is also flagged by actionlint.

Proposed fix

-        uses: actions/checkout@v2
+        uses: actions/checkout@v4

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	uses: actions/checkout@v2
	uses: actions/checkout@v4

🧰 Tools

🪛 actionlint (1.7.10)

[error] 17-17: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🤖 Prompt for AI Agents

In @.github/workflows/internal-image-publish.yaml at line 17, The workflow uses
an outdated action reference "actions/checkout@v2" which pins Node 12 and will
fail; update the checkout step to "actions/checkout@v4" everywhere it appears in
the workflow file (replace the uses: value in the checkout step), commit the
change, and verify any dependent steps still work with the newer checkout
action.