release: v2.3.0 - #49
Merged
Merged
Conversation
chore(release): back-merge v2.2.12 into develop
fix(windows): add UTHelper branding to installer
…al-schedule # Conflicts: # docs/architecture/refactoring-log.md
feat: add Portal daily schedule and polished startup
…ion-tag # Conflicts: # docs/architecture/refactoring-log.md
fix: hiển thị trạng thái chưa làm cho quiz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v2.3.0
SemVer decision
Minor bump
2.2.12 -> 2.3.0: this release adds the backward-compatible Portal daily schedule feature. Installer branding, startup sizing/splash, and quiz status badges are fixes; there are no breaking changes.Included integrations
Verification
ruff check src testspython -m compileall -q src tests scriptsrelease_metadata.py:v2.3.0, build2003000git diff --checkAfter promotion to
main, the same release branch will be merged back intodevelop, then the resulting protectedmaincommit will be taggedv2.3.0.