-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
ci: Increase the timeout on the release process (no-changelog) #6078
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #6078 +/- ##
=======================================
Coverage 18.63% 18.63%
=======================================
Files 2584 2584
Lines 116415 116415
Branches 18180 18180
=======================================
Hits 21689 21689
Misses 94092 94092
Partials 634 634 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
✅ All Cypress E2E specs passed |
* master: feat(core): Manage version control settings (#6079) ci: Fix linting error on `master` (no-changelog) (#6075) ci: Increase the timeout on the release process (no-changelog) (#6078) fix(editor): Update LDAP and Log streaming paywalls (#6069) feat(core): Add instanceId to n8n.ready hook (no-changelog) (#6007) ci: Update linting dependencies, and setup eslint-plugin-unicorn (no-changelog) (#6070)
…rce-mapper-ui-P2 * feature/resource-mapping-component: feat(core): Manage version control settings (#6079) ci: Fix linting error on `master` (no-changelog) (#6075) ci: Increase the timeout on the release process (no-changelog) (#6078) fix(editor): Update LDAP and Log streaming paywalls (#6069) feat(core): Add instanceId to n8n.ready hook (no-changelog) (#6007) ci: Update linting dependencies, and setup eslint-plugin-unicorn (no-changelog) (#6070)
Got released with |
We've had 2 cases of the release process timing out because the build process is taking too long. This puts us at the risk of publishing some of the packages before the job times out, which would a tricky situation to get out of without having to create an empty patch release.