Align Release Tag and `RERUM_API_VERSION`
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript
Research direction
Start by locating the hard-coded 1.0.0 references, the RERUM_API_VERSION environment variable, the __rerum.APIVersion property, and the API version noted on API.html. Compare these sources with the repository's release tags and define a consistent relationship between them. Done means the alignment is decided and reflected across all identified version sources.
Written by the indexing model from the issue text.
Description
The hard coded 1.0.0 tag is still used throughout. We can use that for internal stamping, but we should consider how the release tags and API version align. There is a RERUM_API_VERSION env, a __rerum.APIVersion property, and noted API version on API.html to consider.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 6
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 CenterForDigitalHumanities/rerum_server_nodejs
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
backend dependencies easy
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CenterForDigitalHumanities/rerum_server_nodejs#290 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
All issues in CenterForDigitalHumanities/rerum_server_nodejs
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
521xueweihan/HelloGitHub#3939 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
needs-website-changes
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[Bug] critique requires the detector on native targets, but audit.native.md says it does not applyOpenneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pbakaus/impeccable#1017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day