Skip to content

fix: audit issues, renovate changes[KHCP-21019] - #882

Merged
sharmaadityaHQ merged 16 commits into
mainfrom
fix/audit
Jul 3, 2026
Merged

fix: audit issues, renovate changes[KHCP-21019]#882
sharmaadityaHQ merged 16 commits into
mainfrom
fix/audit

Conversation

@sharmaadityaHQ

@sharmaadityaHQ sharmaadityaHQ commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR aims to fix all audit issues via pnpm audit --fix, renovate PRs and some manual updates to avoid redundant overrides.

  • eslint migration from v9 to v10 by following the migration guide
  • update rollup-plugin-visualizer from v6 to v7. verified by running the pnpm run build:analyzer command. getting a bundle-analyzer/stats-treemap.html file in output.
  • update jsdom from v27 to v29. verified by running all tests.

Consuming app PR - https://github.com/kong-konnect/portal/pull/2580

Jira - https://konghq.atlassian.net/browse/KHCP-21019

Comment thread .npmrc
Comment thread package.json
"vue-router": "^4.6.4",
"vue-tsc": "^3.2.9"
},
"pnpm": {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

issue: we shouldn't be coupling the pnpm v11 upgrade with these other audit fixes. Please split up this PR

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

yes, +1 , it will be much more convenient to track and specially rollback pnpm changes in separate pr.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

created a separate PR for pnpm migration - #890

@sharmaadityaHQ sharmaadityaHQ changed the title fix: audit issues, renovate changes fix: audit issues, renovate changes[KHCP-21019] Jul 3, 2026

@adamdehaven adamdehaven left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

How are you confirming there are no issues from all of these changes?

I'm not sure I understand why all of this needs to go on one pull request

Comment thread package.json
"fast-uri@<=3.1.1": ">=3.1.2",
"uuid@<11.1.1": ">=11.1.1",
"vitest@<3.2.6": ">=3.2.6",
"brace-expansion@>=5.0.0 <5.0.6": ">=5.0.6",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There was previously something breaking across repos when adding brace expansion

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

most of this was via pnpm audit --fix except the 3 changes listed in the PR description. i did 1-2 rounds of manual testing plus consuming PR in portal to check if CI is green there.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

any suggestions on a way we could be more confident that these changes don't break anything?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm just concerned about the brace expansion upgrade but I can't remember what the issue was. Can we verify this works correctly in a portal preview?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

sure, i'll get back with an update here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

it's always better to verify somewhere if unsure -- so creating a draft PR to consume the changes is an easy way to do so. If the draft PR passes and you functionally test in the host repo and things look ok, then you can report back and close the preview

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes, already have the draft PR here - https://github.com/kong-konnect/portal/pull/2580. i'll also do a round of functional testing on a preview portal.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

i did a round of functional testing here - https://pr-2580-portal-ui-dev.konghq.workers.dev/apis/sensitive-data-masking-1/versions/65eb08cc-6e9e-44c1-9c41-ff1066a5aa47 via the consuming PR mentioned in the description of this PR. looks good.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for confirming

@sharmaadityaHQ
sharmaadityaHQ enabled auto-merge (squash) July 3, 2026 18:00
@sharmaadityaHQ
sharmaadityaHQ merged commit ca20e24 into main Jul 3, 2026
11 checks passed
@sharmaadityaHQ
sharmaadityaHQ deleted the fix/audit branch July 3, 2026 18:04
kongponents-bot pushed a commit that referenced this pull request Jul 3, 2026
## [1.107.18](v1.107.17...v1.107.18) (2026-07-03)

### Bug Fixes

* audit issues, renovate changes[KHCP-21019] ([#882](#882)) ([ca20e24](ca20e24))
@kongponents-bot

Copy link
Copy Markdown
Collaborator

🎉 This PR is included in version 1.107.18 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants