-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Only deploy on companion changes #3677
Conversation
@@ -4,6 +4,8 @@ name: Companion Deploy | |||
on: | |||
push: | |||
branches: [main] | |||
paths: | |||
- 'packages/@uppy/companion/**' |
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.
Should we deploy only on Companion releases?
- 'packages/@uppy/companion/**' | |
- 'packages/@uppy/companion/CHANGELOG.md' |
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.
Even better!
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.
I think deploying on changes only would take away from us the advantage of uncovering issues when we deploy to production in case it escapes tests. So I feel like I development version in heroku being up to date is better. What do you think?
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.
but we don't do that anywhere else, we don't publish 'development versions' to the npm registry, so now that I think of it why would the docker version be the exception?
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.
Would it make sense to split the docker publish and heroku deploy jobs? I agree that docker releases make more sense to be aligned with actual Companion releases. But the heroku deploy can use the main branch of Companion, just like examples on the website use the main branch of Uppy.
| Package | Version | Package | Version | | ---------------------- | ------- | ---------------------- | ------- | | @uppy/audio | 0.3.1 | @uppy/provider-views | 2.1.0 | | @uppy/aws-s3 | 2.1.0 | @uppy/react | 2.2.0 | | @uppy/aws-s3-multipart | 2.3.0 | @uppy/react-native | 0.3.0 | | @uppy/companion-client | 2.1.0 | @uppy/screen-capture | 2.1.0 | | @uppy/core | 2.2.0 | @uppy/status-bar | 2.2.0 | | @uppy/dashboard | 2.2.0 | @uppy/svelte | 1.0.8 | | @uppy/drag-drop | 2.1.0 | @uppy/transloadit | 2.2.0 | | @uppy/file-input | 2.1.0 | @uppy/tus | 2.3.0 | | @uppy/google-drive | 2.1.0 | @uppy/url | 2.1.0 | | @uppy/image-editor | 1.2.0 | @uppy/webcam | 2.2.0 | | @uppy/instagram | 2.1.0 | @uppy/xhr-upload | 2.1.0 | | @uppy/locales | 2.1.0 | @uppy/zoom | 1.1.0 | | @uppy/onedrive | 2.1.0 | @uppy/robodog | 2.6.0 | | @uppy/progress-bar | 2.1.0 | uppy | 2.10.0 | - @uppy/audio: fix types (Merlijn Vos / #3689) - @uppy/aws-s3-multipart,@uppy/aws-s3,@uppy/core,@uppy/react,@uppy/transloadit,@uppy/tus,@uppy/xhr-upload: proposal: Cancel assemblies optional (Mikael Finstad / #3575) - @uppy/aws-s3-multipart: export interface AwsS3MultipartOptions (Matteo Padovano / #3709) - @uppy/companion-client: refactor to ESM (Antoine du Hamel / #3693) - @uppy/companion: Only deploy on companion changes (kiloreux / #3677) - @uppy/core: add definition for addFiles method (Matteo Padovano / #3556) - @uppy/core: wrap plugins in div.uppy-Root and set dir attrubute in UIPlugin (Artur Paikin / #3692) - @uppy/google-drive: refactor to ESM (Antoine du Hamel / #3683) - @uppy/image-editor: refactor to ESM (Antoine du Hamel / #3685) - @uppy/instagram: refactor to ESM (Antoine du Hamel / #3696) - @uppy/locales: Add `save` translation to Spanish locale (Juan Carlos Alonso / #3678) - @uppy/locales: refactor to ESM (Antoine du Hamel / #3707) - @uppy/onedrive: refactor to ESM (Antoine du Hamel / #3694) - @uppy/progress-bar: refactor to ESM (Antoine du Hamel / #3706) - @uppy/provider-views: refactor to ESM (Antoine du Hamel / #3715) - @uppy/react: Support React 18 in @uppy/react (Merlijn Vos / #3680) - @uppy/screen-capture: refactor to ESM (Antoine du Hamel / #3698) - @uppy/status-bar: refactor to ESM (Antoine du Hamel / #3697) - @uppy/transloadit: add rate limiting for assembly creation and status polling (Antoine du Hamel / #3718) - @uppy/tus: refactor to ESM (Antoine du Hamel / #3724) - @uppy/url: refactor to ESM (Antoine du Hamel / #3713) - @uppy/webcam: refactor to ESM (Antoine du Hamel / #3686) - @uppy/xhr-upload: refactor to ESM (Antoine du Hamel / #3695) - @uppy/zoom: refactor to ESM (Antoine du Hamel / #3699) - meta: e2e: fix failing test (Antoine du Hamel / #3722) - test: harden linter rule for JSX/ESM validation (Antoine du Hamel / #3681) - test: harden linter rules for ESM/CJS validation (Antoine du Hamel / #3674) - test: Increase retries to trigger longer retryDelay in tus (Artur Paikin / #3726) - test: Remove `it.only` from e2e test (Merlijn Vos / #3690) - tests: Make Cypress more stable & add e2e test for error events when upload fails (Merlijn Vos / #3662)
Only deploy on changes to companion and not every commit to the repo based on this: https://transloadit.slack.com/archives/C0FMW9PSB/p1651238214089669