feat: set-version at publish task #3681
Open
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
kpanot
force-pushed
the
feature/publish-with-version
branch
from
508be60 to
d9fd73e
Compare
|
View your CI Pipeline Execution ↗ for commit 5a7c704
☁️ Nx Cloud last updated this comment at |
github-actions
bot
added
enhancement
kpanot
force-pushed
the
feature/publish-with-version
branch
2 times, most recently
from
8e8c3e6 to
7b382df
Compare
kpanot
force-pushed
the
feature/publish-with-version
branch
from
7b382df to
6b1f15e
Compare
kpanot
force-pushed
the
feature/publish-with-version
branch
4 times, most recently
from
4c2230d to
a1b9945
Compare
fpaul-1A
reviewed
Nov 5, 2025
| "build:swagger-gen": "yarn nx run-many --target=build-swagger", | ||
| "publish": "yarn nx run-many --target=prepare-publish --exclude-task-dependencies && yarn nx run-many --target=publish --exclude=tag:private", | ||
| "publish:extensions": "yarn nx run-many --target=prepare-publish --exclude-task-dependencies && yarn nx run-many --target=publish-extension", | ||
| "publish": "yarn nx run-many --target=publish --exclude=tag:private", |
Contributor
There was a problem hiding this comment.
it's going to rebuild everything on release branches where the cache is disabled, not ideal
Contributor
Author
There was a problem hiding this comment.
If the disable remote cache is a scenario to take in consideration, I will add a local cache transmission mechanism but factually the publish task requires the build task to be run before so the this dependency should remain to avoid mutated dist folder
Contributor
There was a problem hiding this comment.
we actually disable the cache entirely on releases, not just remote cache
Contributor
Author
There was a problem hiding this comment.
I have then changed from local cache disabling to a remote cache only
fpaul-1A
reviewed
Nov 5, 2025
sdo-1A
reviewed
Nov 5, 2025
kpanot
force-pushed
the
feature/publish-with-version
branch
4 times, most recently
from
f434d0e to
b1d1368
Compare
kpanot
force-pushed
the
feature/publish-with-version
branch
10 times, most recently
from
510e4ce to
4b3ab98
Compare
kpanot
force-pushed
the
feature/publish-with-version
branch
from
4b3ab98 to
5a7c704
Compare
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.
Proposed change
feat: set-version at publish task
Related issues
- No issue associated -