Commit Graph

9 Commits

Author SHA1 Message Date
Harminder Virk
552dc52228 test: use shared as integration-tests level (#12278) 2025-04-28 18:41:19 +05:30
Oli Juhl
67e2e718e9 chore: Trigger staging update on new release (#10259) 2024-11-26 09:13:33 +01:00
Riqwan Thamir
1185be31c4 fix: incorrect changeset breaks preview builds (#10173) 2024-11-20 09:41:40 +00:00
Riqwan Thamir
20d19c1d67 chore: update slack message (#9290) 2024-10-15 07:47:13 +00:00
Riqwan Thamir
56fcec3bac chore: notify slack on failed release (#9289) 2024-09-24 17:22:18 +00:00
Harminder Virk
6fa364d728 ci: remove unsupported scripts-prepend-node-path command (#7499) 2024-05-28 13:36:49 +02:00
Harminder Virk
ef6d748784 feat: add Filesystem util and load env util (#7487) 2024-05-28 15:31:13 +05:30
Oli Juhl
2e42e053d4 chore: Publish preview release + deploy staging every 3 hours (#7341)
* wip

* Wrap up

* Update .github/workflows/trigger-staging-deployment.yml

Co-authored-by: Sebastian Rindom <skrindom@gmail.com>

* enable schedule

---------

Co-authored-by: Sebastian Rindom <skrindom@gmail.com>
2024-05-16 12:36:30 +02:00
Oli Juhl
16528c57b0 chore: Introduce release notes formatting + preview release action (#7247)
### What
- Add changelog formatting file to automate pull request categorization in release notes*
- Add action to trigger preview releases
- Remove unused staging deployment action

**Add changelog formatting file to automate pull request categorization in release notes**

In order for this work, we need to be more strict about our labels usage. More specifically, we need to add one of the four different labels noted in the `release.yml` file. The labels should be self-explanatory. If your PR introduces both features and bugs, you should choose the label based on importance of the changes.
2024-05-06 12:59:37 +00:00