Skip to content
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

Bump NcVue to v8.6.2 #43438

Merged
merged 1 commit into from Feb 7, 2024
Merged

Bump NcVue to v8.6.2 #43438

merged 1 commit into from Feb 7, 2024

Conversation

JuliaKirschenheuter
Copy link
Contributor

Bump NcVue to v8.6.2

@@ -4231,6 +4231,18 @@
"npm": "^9.0.0"
}
},
"node_modules/@nextcloud/vue/node_modules/@nextcloud/router": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now doubling the dependencies of router, might be bad. Can we update @nextcoud/router for server in the package.json as well? So we only use one version.

Copy link
Contributor

@ShGKme ShGKme Feb 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then we need to update it literally everywhere. @nextcloud/axios, @nextcloud/dialogs, @nextcloud/files, @nextcloud/password-confirmation, @nextcloud/upload

Let's only update the @nextcloud/vue first. @nextcloud/router is stateless and small, should not be an issue.

Then we can update all the dependencies

Signed-off-by: julia.kirschenheuter <julia.kirschenheuter@nextcloud.com>
@Pytal Pytal enabled auto-merge February 7, 2024 19:15
@Pytal Pytal merged commit 0395cd8 into master Feb 7, 2024
85 checks passed
@Pytal Pytal deleted the bump/bump-ncvue-to-v8.6.2 branch February 7, 2024 19:36
artonge pushed a commit that referenced this pull request Feb 8, 2024
@blizzz blizzz mentioned this pull request Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants