chore(build): Remove version numbers from build artifact names
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- build-system
Research direction
Start by tracing the build process that produces the built JS files and compare its artifact names with the test reference in test/unit/spec/main.html, cited in the linked UseraleJS issue. Done means built artifact names no longer contain version numbers, while NPM and Apache release channels continue to include them; verify the test suite no longer depends on versioned filenames.
Written by the indexing model from the issue text.
Description
Copied from https://github.com/apache/flagon-useralejs/issues/506
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.
- Dominant language
- Jupyter Notebook
- Stars
- 30
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/flagon
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
process
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Discuss enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement experimental
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
enhancement Userale
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
espressif/esp-matter#1874 ·
-
cudev: Fix MSVC build failures with 64-bit integers (int64_t/uint64_t) in vec_traits.hppPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opencv/opencv_contrib#4231 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
linux-test-project/lcov#552 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Package: Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getsolus/packages#10933 · 1 comment ·
Maintainers usually reply within 1 day