cargo release helper #790
No reviewers
標籤
未選擇標籤
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
未選擇里程碑
No project
No assignees
2 participant
訊息
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#790
載入中…
Add table
Reference in a new issue
No description provided.
Delete branch "igalic/fix/cargo-release-helper"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
how to use?
Codecov Report
uh… will we need to add it as development dependency?
Shouldn't the repo URL be changed here?
Also, maybe we could unify the headers in the changelog to follow what https://keepachangelog.com/ recommends, to keep it coherent.
And for the development dependency, I don't think so. It should be documented here that people who want to publish a new release should use this tool tho.
how?
To something like
https://github.com/Plume-org/Plume/compare/{{tag_name}}...HEAD
, so that the changelog links to our commit history.Also, is there a
<!-- next-url -->
somewhere in the changelog you added? I can't find it.n. b. : i've back-filled the changelog by copy-pasting the text from our github releases page
for the future of the changelog, i absolutely agree
I know you copied what is on GitHub, but maybe we could change this text? Would it be a problem to have texts that are a bit different on Github and in the changelog? I would prefer to have the whole changelog have the same format (but that's arguable).
Also, could it be possible to add
pre-release-hook
to runcrowdin pull
(I don't remember the exact arguments, but basically : the command to pull the latest version of translations)? Or do you think it should be done manually before runningcargo release
?the only problem was time and energy
y'all have access to write to this PR, so, please, by all means, help me!!
that's a very good idea!
how do i make it work?
I don't remember how the Crowdin CLI works, I'll check that and edit the PR. I'll also edit the changelog.
So the translations should be pulled now, if you have a
CROWDIN_API_KEY
in your env. We should remember to document how to get one before making a release.let's create a doc issue right now, and link it here
https://github.com/Plume-org/docs/issues/88
what about docker?
I think the release should be automatic, I'll check.
It is not, I'll a hook.
The thing is, the docker tag needs to be pushed after the git tag, and there is no
post-release-hook
in cargo release, apparently.So maybe we can document that this has to be done manually, and do it by hand for the moment?
or we could add docker tag to the CI build process, only on tag
yunohost relies on docker, right?
and it's one of the platforms that we recommend, thru our installation guide
It doesn't, it uses Bash scripts. I'm not sure if it is better tho… 😅
i didn't add it to our current changelog
We can tag to Docker images automatically by setting automate build properly.
A test succeeded:
(v0.5.1-test2 was pushed by plumeorg)
Remaining issue is how do we notify YunoHost maintainer. It is not an issue of cargo helper (this pul request's theme) but an issue of CI. So this pull request is ready to be merged.
Closed as #835
Pull request closed