-
Notifications
You must be signed in to change notification settings - Fork 7.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
feat(core): Only show V1 banner to users who migrated #6622
feat(core): Only show V1 banner to users who migrated #6622
Conversation
Signed-off-by: Oleg Ivaniv <me@olegivaniv.com>
Great PR! Please pay attention to the following items before merging: Files matching
Files matching
Files matching
Make sure to check off this list before asking for review. |
Signed-off-by: Oleg Ivaniv <me@olegivaniv.com>
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #6622 +/- ##
==========================================
- Coverage 28.91% 28.85% -0.06%
==========================================
Files 3069 3069
Lines 188334 188355 +21
Branches 20889 20890 +1
==========================================
- Hits 54454 54355 -99
- Misses 133000 133120 +120
Partials 880 880 ☔ View full report in Codecov by Sentry. |
Passing run #1401 ↗︎
Details:
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
✅ All Cypress E2E specs passed |
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.
Looks like another bad migration slipped through @n8n-io/migrations-review . Sorry about that.
@@ -154,6 +154,11 @@ export class CreateUserManagement1646992772331 implements ReversibleMigration { | |||
await queryRunner.query( | |||
`INSERT INTO ${tablePrefix}settings (\`key\`, value, loadOnStartup) VALUES ("userManagement.isInstanceOwnerSetUp", "false", 1), ("userManagement.skipInstanceOwnerSetup", "false", 1)`, | |||
); | |||
|
|||
await queryRunner.query(` | |||
INSERT INTO "${tablePrefix}settings" (key, value, loadOnStartup) |
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.
this query is invalid for mysql.
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.
@netroy 🤦 My bad, this should fix it https://github.com/n8n-io/n8n/pull/6628/files
* ADO-814-trial-banner: 👕 Fixing lint errors ✔️ Removing store import from API file ⚡ Updating banners dimensions on resize, removing leftover code refactor: Stop using `.d.ts` files for type-collection files (no-changelog) (#6634) fix(core): Fix credentials lazy-loading (no-changelog) (#6615) ci: Upgrade `tough-cookie` to address CVE-2023-26136 (no-changelog) (#6630) feat(editor): Load fixed template list as experiment (#6632) ✅ Added more banner tests feat(Slack Node): Add option to include link to workflow in Slack node (#6611) fix(editor): Extend menu item and use it as a recursive component (#6618) fix: Add postAuthenticate hook for source control preferences (no-changelog) (#6629) ✔️ Fixing failing banner tests ci: Fix v1 banner migration (no-changelog) (#6628) ✅ Added banners unit tests ✔️ Updating testing endpoints to use new store data fix(Code Node): Install python modules always in a user-writable folder (#6568) feat(core): Only show V1 banner to users who migrated (#6622) 💄 Tweaking zoom to fit position ✔️ Updating Callout component test snapshots 👕 Fixing linting errors
* feat(editor): Only show V1 banner to users who migrated Signed-off-by: Oleg Ivaniv <me@olegivaniv.com> * Set the v1 banner dismissed flag in settings table create migration Signed-off-by: Oleg Ivaniv <me@olegivaniv.com> --------- Signed-off-by: Oleg Ivaniv <me@olegivaniv.com>
Got released with |
We want to show the V1 banner only to the users that came from a pre-V1 version. To do this, we set a flag in the database in the migration script where the settings table is created.
Github issue / Community forum post (link here to close automatically):