Enable auto publish #302
Merged
Enable auto publish #302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
angeliski
force-pushed
the
enable-auto-publish
branch
2 times, most recently
from
82101d5 to
708fffa
Compare
angeliski
force-pushed
the
enable-auto-publish
branch
from
708fffa to
26e6ea1
Compare
angeliski
force-pushed
the
enable-auto-publish
branch
2 times, most recently
from
9f5b84f to
495bb5f
Compare
angeliski
force-pushed
the
enable-auto-publish
branch
from
495bb5f to
2b4d6f1
Compare
angeliski
force-pushed
the
enable-auto-publish
branch
from
c609c0c to
b02e076
Compare
angeliski
force-pushed
the
enable-auto-publish
branch
from
6cdc646 to
045ada9
Compare
|
@angeliski , depois dessas modificações, há alguma previsão de publicação da versão 2.1.7? Tenho muito interesse nos últimos merges realizados. |
|
Opa mestre, achei que tivesse feito o release. Pode deixar que eu vou ver pra fazer hoje a noite |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Descrição
Esse PR modifica os workflows para facilitar a publicação de uma nova versão. Agora é possivel via Actions disparar um fluxo para o release. A versão será publicada em staging e será necessário liberar o release no Nexus, isso para garantir que não haja nenhum acidente na liberação.
Inicialmente o fluxo seria controlado via Release do GH, mas devido a limitações da estrutura eu decidi utilizar apenas o trigger normal, no futuro isso pode ser revisto.
As credencias cadastradas são todas minhas, para facilitar o fluxo. Se necessário isso pode ser alterado para uma machine account.
Ref:
https://itnext.io/publishing-artifacts-to-maven-central-using-github-actions-a-step-by-step-guide-fd65ef075fd4
https://github.com/marketplace/actions/java-maven-release
https://github.com/teamlead/java-maven-sonatype-starter?tab=readme-ov-file