-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Inf 371 community release workflow #5595
Conversation
@@ -71,28 +115,37 @@ jobs: | |||
--platform=linux/amd64,linux/arm64 --provenance=false | |||
--output=type=image,name=ghcr.io/${{ env.REGISTRY_OWNER }}/${{ env.SERVICE_NAME }},push-by-digest=true,name-canonical=true | |||
run: | | |||
cd apps/$SERVICE_NAME && pnpm run docker:build | |||
if [ "${{ env.SERVICE_NAME }}" = "embed" ] || [ "${{ env.SERVICE_NAME }}" = "embed-ee" ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are currently a few services/apps without the enterprise functionality, so they are not different from the community build, and embed is one of these... however, the embed leaves in a different folder under the libs
that's why we have this code... embed is a static JS script that is served with the http-server
Hey there and thank you for opening this pull request! 👋 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Your PR title is: Details:
|
What changed? Why was the change needed?
These changes are needed for monthly community releases. It will create a new workflow (WF) to build a community version of docker images for multiple architectures.
Currently, we assume to bump the Lerna release version manually.
How does this WF work?
When we run
pnpm release:xxxxx
and Lerna creates a git tag the workflow will be triggered automatically to build docker images with the same docker tag as the git tag and the lerna version.