Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Version '1.12.1' into 'master' Branch #156

Merged
merged 35 commits into from
Feb 2, 2024
Merged

Release Version '1.12.1' into 'master' Branch #156

merged 35 commits into from
Feb 2, 2024

Conversation

github-actions[bot]
Copy link
Contributor

🚀 Release '1.12.1' into 'master' Branch 🚀

This PR marks a pivotal moment in our deployment cycle, signaling that all changes on the Release branch are deemed ready for production. It represents the collective decision of our developers that the changes bundled in the Release are suitable to be released together.

What's Happening in This PR?

  • We are merging the 'release' branch into the 'master' branch.
  • This action is a critical step, transitioning us from the release phase to the production phase.

✅ Automatic Merging Upon CI Checks ✅

This PR will be automatically merged into the 'master' branch, if the following conditions are met:

  • All CI Checks pass
  • Code Review is approved by at least one developer

⚠️ Manual Merging Upon CI Checks and Code Review ⚠️

If the above conditions are not met, this PR will be manually merged into the 'master' branch, by a developer.

github-actions bot and others added 18 commits January 28, 2024 12:50
…elease-train Branch (#149)

* ci(gitops): 1-click boarding on Release Train

ci(gitops): mention User's branch name in PR title

ci(gitops): debug why train branch is missing

ci(gitops): use origin/release-train to merge 'boarding' branch into

ci(gitops): use local refs for PR, and include sanity check prior to opening PR

ci(gitops): try to trigger Boarding CI Checks, related to PR --> 'release-train', by pushing 'boarding' br after PR open

ci(gitops): trigger on PR from boarding to release-train for for test.yaml Workflow

ci(gitops): use pat, instead of GITHUB_TOKEN, to trigger CI/CD Pipeline in push from Workflow code

ci(gitops): use pat, instead of GITHUB_TOKEN, to trigger CI/CD Pipeline in push from Workflow code

ci(gitops): do do git push 'boarding' branch after PR opens

ci(gitops): write proper Markdown content for PR Body

ci(gitops): automatically merge boarding --> release-train PR, once CI Checks Pass

ci(gitops): fix Boarding Train event trigger

ci(gitops): fix logic of condition to create Release Train

ci(gitops): if Upstream Release Train exists, pull it

ci(gitops): debug release train branch track upstream error

ci(gitops): fix condition when release train does NOT exist

ci(gitops): fix condition when release train does NOT exist

ci(gitops): improve load bash script

ci(gitops): improve load bash script

* ci(gitops): add shell script to trigger RC Tests on CI

* ci(gitops): handle branches on local dev machine

* ci(gitops): start rt by only updating release branch, local and upstream

* ci(gitops): make bash script non-interactive

* ci(gitops): improve bash script

* ci(gh-release): add Job for `gh release create`, and trigger load-to-rt on 'auto-release' tag

* chore(start-rt): document option for CLI solution with shell for simple interaction, or with python

* ci(gitops): automatically 'board' and 'start' Release Train, on 'boarding-n-auto-release' pushed tag

* style(comments): clean code, by removing obsolete code comments about cookiecutter callable

* refactor(black): apply black

* test(log-file): expect either empty log file in PWD, after generator run, or no file at all

* refactor(black): apply black

---------

Co-authored-by: konstantinos <[email protected]>
Co-authored-by: Konstantinos Lampridis <[email protected]>
ci(gitops): try to fix, by tracking Upstream 'release' branch before checking tag

ci(gitops): print git log before checking if tag is on release branch

ci(gitops): fix false negative

ci(gitops): add script for automatic Sem Ver source code update

ci(gitops): chmod +x script in CI workflow

ci(gitops): configure git user.name and user.email before

ci(gitops): fix path to parse_version.py and use sh as entrypoint to distro-sem-ver-bump.sh

ci(gitops): properly git revert to commit with Prod Sem Ver after -rc tests
Copy link

codecov bot commented Jan 29, 2024

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (c628b63) 83.08% compared to head (fbb0513) 80.98%.

Files Patch % Lines
...napshots/biskotaki-gold-standard/tests/test_cli.py 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #156      +/-   ##
==========================================
- Coverage   83.08%   80.98%   -2.10%     
==========================================
  Files          77       76       -1     
  Lines        1986     1599     -387     
==========================================
- Hits         1650     1295     -355     
+ Misses        336      304      -32     
Flag Coverage Δ
unittests 80.98% <75.00%> (-2.10%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

boromir674
boromir674 previously approved these changes Jan 29, 2024
…t Job, instead of Matrix for pushed v* tags\n\nThis reverts commit .
@boromir674 boromir674 merged commit df69397 into master Feb 2, 2024
14 of 17 checks passed
@boromir674 boromir674 deleted the release branch February 2, 2024 15:38
@boromir674 boromir674 restored the release branch February 2, 2024 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant