Update release actions to use master to trigger

[minyiky]

No description provided.

[coderabbitai]

Walkthrough

The pull request updates .github/workflows/release_actions.yml by changing the branch trigger for the “Publish Docker image” workflow from main to master. No other workflow steps, jobs, or configuration elements are modified. There are no alterations to exported or public interfaces.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A twitch of whiskers, a branch swap faster—
From main I hop to trusty master.
Docker sails when tags align,
Carrots cached, the build is fine.
Thump-thump—release day’s hare-ly vaster! 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request has no description while the repository template requires "Summary", "Testing", and "Trade‑offs and Alternatives" sections; this omission leaves reviewers without context about why the workflow trigger was changed, what testing was performed, and whether there are any trade‑offs.	Please populate the PR description following the repository template: add a Summary explaining why the release Actions trigger was changed and reference .github/workflows/release_actions.yml, add a Testing section describing CI runs or manual tests performed, and add a Trade‑offs and Alternatives section or state it is not applicable; include links to related issues or CI logs where relevant.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Update release actions to use master to trigger" clearly and concisely summarises the primary change—switching the release Actions workflow trigger from 'main' to 'master'—and matches the modification in .github/workflows/release_actions.yml, so it accurately reflects the main change and is appropriate for reviewers.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch minyiky/fix-release-action

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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: 0

🧹 Nitpick comments (2)

.github/workflows/release_actions.yml (2)

3-6: Verify default branch; consider supporting both master and main (plus manual trigger).

If the repo’s default branch is still main, this workflow will never run. To be safe during/after branch renames, include both branches and add a manual workflow_dispatch trigger.

 on:
   push:
     branches:
-      - master
+      - master
+      - main
+  workflow_dispatch:

---

18-18: Pin third‑party Actions to commit SHAs.

For release workflows that publish artefacts, pin actions/checkout, docker/login-action, and docker/build-push-action to specific commit SHAs to reduce supply‑chain risk. Keep a comment with the corresponding tag for readability.

Also applies to: 25-25, 32-32, 47-47

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0606d90 and 71f61b0.

📒 Files selected for processing (1)

• .github/workflows/release_actions.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)

• GitHub Check: qemu_riscv64
• GitHub Check: standard_v2
• GitHub Check: sanitize_undefined
• GitHub Check: settrace_stackless
• GitHub Check: macos
• GitHub Check: gil_enabled
• GitHub Check: stackless_clang
• GitHub Check: qemu_mips
• GitHub Check: nanbox
• GitHub Check: coverage_32bit
• GitHub Check: longlong
• GitHub Check: build_stm32 (stm32_misc_build)
• GitHub Check: build_stm32 (stm32_nucleo_build)
• GitHub Check: build_stm32 (stm32_pyb_build)
• GitHub Check: build_idf (esp32_build_c2_c6)
• GitHub Check: build_idf (esp32_build_s3_c3)
• GitHub Check: build
• GitHub Check: build_idf (esp32_build_cmod_spiram_s2)
• GitHub Check: build
• GitHub Check: build

[github-actions]

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32