nextcloud / nextcloud/notify_push
The latest tag still points to version 1.3.0
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
The latest tag still points to version 1.3.0
Hi, the container image with the latest tag still points to the previous version 1.3.0 and not the latest version 1.3.1.
The NextCloud Notify app is already updated to version 1.3.1, so the latest tag causes a mismatch between the server version and the NextCloud Notify app, causing some errors in testing.
Thank you.
Contributor 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.
Research direction
No file or test is named. Start by locating the container-image publishing and version-tag configuration, then compare how versions 1.3.0 and 1.3.1 are released; done means the latest image tag points to 1.3.1 and matches the updated NextCloud Notify app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100