-
Notifications
You must be signed in to change notification settings - Fork 277
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
fix: report correct package version in the source code #2566
Merged
MartinCupela
merged 2 commits into
master
from
chore/build-with-correct-latest-package-version
Dec 2, 2024
Merged
fix: report correct package version in the source code #2566
MartinCupela
merged 2 commits into
master
from
chore/build-with-correct-latest-package-version
Dec 2, 2024
Conversation
This file contains 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
MartinCupela
requested review from
oliverlaz,
myandrienko and
arnautov-anton
November 21, 2024 10:04
Size Change: -69 B (-0.01%) Total Size: 1.16 MB
ℹ️ View Unchanged
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2566 +/- ##
==========================================
- Coverage 83.23% 83.22% -0.01%
==========================================
Files 439 438 -1
Lines 9142 9140 -2
Branches 2237 2237
==========================================
- Hits 7609 7607 -2
Misses 1205 1205
Partials 328 328 ☔ View full report in Codecov by Sentry. |
oliverlaz
approved these changes
Nov 21, 2024
MartinCupela
deleted the
chore/build-with-correct-latest-package-version
branch
December 2, 2024 12:14
github-actions bot
pushed a commit
that referenced
this pull request
Dec 2, 2024
## [12.6.1](v12.6.0...v12.6.1) (2024-12-02) ### Bug Fixes * report correct package version in the source code ([#2566](#2566)) ([2157d2f](2157d2f))
🎉 This PR is included in version 12.6.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🎯 Goal
Report the correct package version in
useChat.ts
hook.🛠 Implementation details
During the release process the correct latest package version can be determined only while
semantic-release
is run. This is becausesemantic-release
infers the next version. The bundle script now takes into consideration theNEXT_VERSION
env variable value set during thesemantic-release
process run. If this value is not set, then the version is calculated from the current latest git tag - that is useful for local builds. Otherwise the fallback is package.jsonversion
that is not maintained, but such fallback should actually be never executed.We are removing the
version.ts
file andcopy-version.sh
script as this script was run before the version could be calculated.