novu
novu copied to clipboard
Inf 371 community release workflow
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?
- Get the Novu release version from lerna.json and check whether the git tag exists or not. If it exists the return message about it. If the Tag wasn't created yet then the WF will create the tag in the end.
- Build the docker images, tag and push them to the GHCR
- If the images were built successfully the last step of the WF will tag the current commit of the current branch by using the TAG that was got on the first step.
Deploy Preview for dev-web-novu ready!
Name | Link |
---|---|
Latest commit | 70ccbd1a2ed17a37da4fdab9bb65d3052ecf0996 |
Latest deploy log | https://app.netlify.com/sites/dev-web-novu/deploys/664b584d374f4d00083f086a |
Deploy Preview | https://deploy-preview-5595--dev-web-novu.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Deploy Preview for novu-design ready!
Name | Link |
---|---|
Latest commit | 70ccbd1a2ed17a37da4fdab9bb65d3052ecf0996 |
Latest deploy log | https://app.netlify.com/sites/novu-design/deploys/664b584d8ba9640009939208 |
Deploy Preview | https://deploy-preview-5595--novu-design.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Honestly, you've been holding me hostage for months
On Fri, May 17, 2024 at 9:35 AM netlify[bot] @.***> wrote:
👷 Deploy Preview for dev-web-novu processing. Name Link 🔨 Latest commit f35e32c https://github.com/novuhq/novu/commit/f35e32c65deb89c34da7b18ee094aab0944fd180 🔍 Latest deploy log https://app.netlify.com/sites/dev-web-novu/deploys/66475d040b847d00083e1ac0
— Reply to this email directly, view it on GitHub https://github.com/novuhq/novu/pull/5595#issuecomment-2117623963, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDAW5TNTDHY4ENVKFKBENLLZCYBTRAVCNFSM6AAAAABH4FGPX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJXGYZDGOJWGM . You are receiving this because you are subscribed to this thread.Message ID: @.***>
you started changing the business documents then the phones PC mail, then me money then my wife who said it had nothing to do with it..!!! Why !!?
On Fri, May 17, 2024 at 9:38 AM netlify[bot] @.***> wrote:
👷 Deploy Preview for novu-design processing. Name Link 🔨 Latest commit f35e32c https://github.com/novuhq/novu/commit/f35e32c65deb89c34da7b18ee094aab0944fd180 🔍 Latest deploy log https://app.netlify.com/sites/novu-design/deploys/66475d041f6a90000816395c
— Reply to this email directly, view it on GitHub https://github.com/novuhq/novu/pull/5595#issuecomment-2117628836, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDAW5TNOJUCEGYDOFHVNRCDZCYB5DAVCNFSM6AAAAABH4FGPX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJXGYZDQOBTGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
you organized everything just to hurt me!
On Fri, May 17, 2024 at 9:47 AM Giacomo Lazzano < @.***> wrote:
you started changing the business documents then the phones PC mail, then me money then my wife who said it had nothing to do with it..!!! Why !!?
On Fri, May 17, 2024 at 9:38 AM netlify[bot] @.***> wrote:
👷 Deploy Preview for novu-design processing. Name Link 🔨 Latest commit f35e32c https://github.com/novuhq/novu/commit/f35e32c65deb89c34da7b18ee094aab0944fd180 🔍 Latest deploy log https://app.netlify.com/sites/novu-design/deploys/66475d041f6a90000816395c
— Reply to this email directly, view it on GitHub https://github.com/novuhq/novu/pull/5595#issuecomment-2117628836, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDAW5TNOJUCEGYDOFHVNRCDZCYB5DAVCNFSM6AAAAABH4FGPX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJXGYZDQOBTGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
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: Inf 371 community release workflow
It should be something like: feat(scope): Add fancy new feature
Details:
No release type found in pull request title "Inf 371 community release workflow". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/
Available types:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit