ci: auto set dxt version on release #244
Merged
Conversation
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
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
c0831a6 to
6040d12
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
62021e9 to
5e5c477
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
cb07611 to
d9bda2c
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
634cfb9 to
9478ff5
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
52ed596 to
073cbaf
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
3622d32 to
3bff84d
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
39d3074 to
ce00993
Compare
MQ37
force-pushed
the
ci/auto-set-dxt-version
branch
from
4c1d622 to
98a193d
Compare
jirimoravcik
approved these changes
Aug 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
closes #229
Added automatic version update also for the
manifest.json. Also figured out we were accessing the new git committed ref with the.jsonupdates incorrectly and it could cause we were releasing packages with wrong version number. Fixed this and also added checks to prevent this in future.