New CI

[rimu-stack]

Новый workflow:

• Ветка dev → тег dev (актуальное состояние разработки)
• Ветки release-* → тег beta (кандидаты для стабилизации)

[Copilot]

Pull request overview

This PR introduces a new CI workflow structure that separates development and release candidate builds. The dev branch now builds images with the dev tag, while release-* branches build images with the beta tag for stabilization candidates.

Changes:

• New workflow file build-dev.yml for building development images from the dev branch
• Updated build-beta.yml to trigger on release-* branches instead of dev branch

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
.github/workflows/build-dev.yml	New workflow that builds and tags images with dev tag when pushing to the dev branch
.github/workflows/build-beta.yml	Updated branch trigger from dev to release-* pattern to build beta-tagged images

Comments suppressed due to low confidence (4)

.github/workflows/build-beta.yml:70

• Corrected spelling of 'enviroment' to 'environment'.

      - name: run test enviroment

.github/workflows/build-beta.yml:74

• Corrected spelling of 'enviroment' to 'environment'.

      - name: shutdown test enviroment

.github/workflows/build-beta.yml:75

• The shutdown step is using 'docker compose up -d' instead of 'docker compose down'. This will start containers instead of stopping them, leaving the test environment running.

        run: cd integration_tests/ssh && docker compose up -d

.github/workflows/build-beta.yml:125

• Reference to undefined variable TAG2. This variable is not defined in the environment and will echo an empty string.

          echo $TAG2

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.