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

Release v0.9.5 #1711

Merged
merged 20 commits into from
Mar 23, 2023
Merged

Release v0.9.5 #1711

merged 20 commits into from
Mar 23, 2023

Conversation

dependabot bot and others added 20 commits March 15, 2023 12:07
Bumps [webpack](https://github.com/webpack/webpack) from 5.9.0 to 5.76.0.
- [Release notes](https://github.com/webpack/webpack/releases)
- [Commits](webpack/webpack@v5.9.0...v5.76.0)

---
updated-dependencies:
- dependency-name: webpack
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Test change namespace copy namespace directory
…ite/webpack-5.76.0

Bump webpack from 5.9.0 to 5.76.0 in /website
Test server release 704e7c3

# Conflicts:
#	website/yarn.lock
@amvanbaren amvanbaren self-assigned this Mar 22, 2023
@kineticsquid
Copy link
Contributor

I tested the Namespace rename in staging as follows:

  • simple rename
  • rename and merge
  • rename and do not remove original namespace

All worked as intended with one minor issue. When namespace are merged and a publisher is in both, that publisher shows up twice in the merged namespace. @amvanbaren noted that this can also happen for an extension. I've documented this in eclipse/openvsx#716.

@kineticsquid
Copy link
Contributor

Otherwise, I'm good with proceeding with the deployment.

@amvanbaren amvanbaren merged commit e9b5cb5 into production Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants