-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create workflows to release Node.js adapter from own repo #520
Comments
I think the release.sh script is likely not used any longer and can be removed, the release is done from the workflow under |
mposolda
added a commit
to mposolda/keycloak-nodejs-connect
that referenced
this issue
Dec 10, 2024
closes keycloak#520 Signed-off-by: mposolda <[email protected]>
mposolda
added a commit
to mposolda/keycloak-nodejs-connect
that referenced
this issue
Dec 13, 2024
closes keycloak#520 Signed-off-by: mposolda <[email protected]>
mposolda
added a commit
to mposolda/keycloak-nodejs-connect
that referenced
this issue
Dec 16, 2024
closes keycloak#520 Signed-off-by: mposolda <[email protected]>
mposolda
added a commit
to mposolda/keycloak-nodejs-connect
that referenced
this issue
Dec 16, 2024
closes keycloak#520 Signed-off-by: mposolda <[email protected]> Co-authored-by: Jon Koops <[email protected]> Signed-off-by: Marek Posolda <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It can be good to have GH workflow, which will allow to release node.js from it's own repository .
NOTE (hint): It looks that there is already script release.sh, so perhaps that one is OK to be re-used in the workflow?
I guess this is used by the GH workflow, which is currently triggered from keycloak-rel during keycloak server release (We are going to remove releasing of node.js from keycloak-rel as we want to decouple node.js adapter release from keycloak-server release. Related task for decouple node.js release from keycloak-rel is keycloak/keycloak#35536 )
The text was updated successfully, but these errors were encountered: