You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2025. It is now read-only.
Build artifact names contain the version number. This creates a dependency between our test suite (see here, for example) and the version number. Not only is this a blocker for automation, it will create flaky tests on every release.
Solution
Remove version numbers from the build artifact name. The only place version numbers need be included is on the release channels (NPM, apache), not in built js files themselves.
The text was updated successfully, but these errors were encountered:
Hey @Suvendu-UI. I should've been more clear in this ticket. The reason the version keeps showing up in the build artifacts when you run npm run build is because it is our build tool, rollup, that's configured to interpolate the version number into the created file names.
See here in our rollup.config.js file. This is what needs to be removed in order to remove the version number from the build artifact names.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Good First IssueStuff for folks new to projectProcessASF- or Project-Driven Release Processes
Problem
Build artifact names contain the version number. This creates a dependency between our test suite (see here, for example) and the version number. Not only is this a blocker for automation, it will create flaky tests on every release.
Solution
Remove version numbers from the build artifact name. The only place version numbers need be included is on the release channels (NPM, apache), not in built js files themselves.
The text was updated successfully, but these errors were encountered: