You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ITEP-68209] Add parsing of version.txt for rc version for build (#236)
## 📝 Description
This PR adds parsing logic for release candidate (RC) versions from
version.txt file in the build workflow. It modifies the weekly build
workflow to handle RC versions differently by using the version.txt
content directly as the image tag when it contains "rc".
Key Changes:
- Added error handling when version.txt file is not found
- Added conditional logic to detect RC versions and use them directly as
image tags
- Modified existing tag generation logic to accommodate RC version
handling
<!--
If the PR addresses a specific GitHub issue, include one of the
following lines to enable auto-closing:
Fixes #<issue_number>
Closes #<issue_number>
If referencing an internal ticket (e.g. JIRA), include the ticket number
instead:
JIRA: <project-key>-<ticket-number>
If there’s no related issue or ticket, you can skip this section.
-->
## ✨ Type of Change
Select the type of change your PR introduces:
- [ ] 🐞 **Bug fix** – Non-breaking change which fixes an issue
- [ ] 🚀 **New feature** – Non-breaking change which adds functionality
- [ ] 🔨 **Refactor** – Non-breaking change which refactors the code base
- [ ] 💥 **Breaking change** – Changes that break existing functionality
- [ ] 📚 **Documentation update**
- [ ] 🔒 **Security update**
- [ ] 🧪 **Tests**
- [ ] 🚂 **CI**
## 🧪 Testing Scenarios
Describe how the changes were tested and how reviewers can test them
too:
- [ ] ✅ Tested manually
- [ ] 🤖 Ran automated end-to-end tests
## ✅ Checklist
Before submitting the PR, ensure the following:
- [ ] 🔍 PR title is clear and descriptive
- [ ] 📝 For internal contributors: If applicable, include the JIRA
ticket number (e.g., ITEP-123456) in the PR **title**. Do **not**
include full URLs
- [ ] 💬 I have commented my code, especially in hard-to-understand areas
- [ ] 📄 I have made corresponding changes to the documentation
- [ ] ✅ I have added tests that prove my fix is effective or my feature
works
0 commit comments