forked from n8n-io/n8n
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updates #41
Merged
Merged
Updates #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* ⚡ DateTime node improvements * 🔨 Fix parsing format in date calculation * ⚡ Small improvements * ✏️ Rename params and add tooltips * 🔨 Reorder params * ⚡ Set default values * ⚡ Set defaults and use same parameter name Co-authored-by: ricardo <ricardoespinoza105@gmail.com> Co-authored-by: Jan Oberhauser <jan.oberhauser@gmail.com>
* ✨ Google BigQuery node * 🔨 Add comment dividers * ⚡ Add whitespace for readability * ✏️ Edit resource descriptions * ⚡ Improvements Co-authored-by: Iván Ovejero <ivov.src@gmail.com>
…uest node (#1650) * Added a global timeout setting for all http requests except for http node. The http node explicitly sets a timeout that overrides the default value. This is to prevent behaviors when users were expecting that their quests could take a very long time to execute. * Removed unnecessary typing from code
#1634) * Implemented timeout for workers and corrected timeout for subworkflows * Fixed issue with timeouts when running on separate processes * Standardized timeouts across all n8n Now the maxTimeout setting takes effect whenever a timeout is set to any workflows. This causes local timeouts (either set on a per-workflow basis or via global settings) to be capped by the maximum timeout. This behavior already existed but was not applied to all places. Also changed the way n8n enforces timeouts for subworkflows, making it work always. In effect, with this change, if you have one workflow that calls others only the main workflow's timeout is taken into consideration, limiting the maximum time that other workflows combined can run. * ⚡ Fix timeout problem in "own" mode Co-authored-by: Jan Oberhauser <jan.oberhauser@gmail.com>
Snyk has created this PR to upgrade moment from 2.28.0 to 2.29.1. See this package in npm: https://www.npmjs.com/package/moment See this project in Snyk: https://app.snyk.io/org/janober/project/a08454f4-33a1-49bc-bb2a-f31792e94f42?utm_source=github&utm_medium=upgrade-pr
* add optimize-svg command to npm scripts * run svgo over all svg assets in repo
…and n8n-workflow@0.56.0 on n8n
* Add get/getAll:User in NextCloud node * Add update/delete:User in NextCloud node * Fix getAll:User operation
) * Add update/delete to Team, Release and Project in SentryIo node * Add create/delete:Project in SentryIo node * Minor fix * Fix descriptions & display names * Fix casing in descriptions * Add getTeams load function & Update operations fields * Change 'Additional Field' to 'Update Fields' for Team,Release,Project & Organization operations
…and n8n-workflow@0.60.0 on n8n
* enable header clicks * remove unused func
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates