Skip to content

Update various packages.#1676

Open
MikeNeilson wants to merge 2 commits intodevelopfrom
devops/package-updates
Open

Update various packages.#1676
MikeNeilson wants to merge 2 commits intodevelopfrom
devops/package-updates

Conversation

@MikeNeilson
Copy link
Copy Markdown
Contributor

Am manually testing the CDA GUI now, wanted to get the rest of the build started.

Manually handles several dependabot/security reports that weren't getting updated by the automation.

@MikeNeilson
Copy link
Copy Markdown
Contributor Author

UI still works, also corrected the behavior for the swagger-docs link, previous fix did not quite do the trick.

@MikeNeilson MikeNeilson force-pushed the devops/package-updates branch from 4e7122b to 6a6657e Compare April 8, 2026 16:14
Copy link
Copy Markdown
Collaborator

@krowvin krowvin left a comment

Choose a reason for hiding this comment

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

Wondering about the version downgrade on the generator before you merge

Comment thread cda-client/package.json
},
"devDependencies": {
"@openapitools/openapi-generator-cli": "^2.15.3",
"@openapitools/openapi-generator-cli": "^0.0.6",
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.

Why are we downgrading the generator? I think we might have picked the wrong version because this could introduce some unforeseen security issues going this far back?

I assumed it might be because of the old javalin/java version but wanted to make sure.

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.

Huh, thanks, didn't catch that. I'm not sure what happened there, I ran npm audit fix --force might have had something to do with the force, but definitely going backwards there.

Comment thread cda-gui/src/main.jsx
globalThis.location.replace(h);
return null;
},
component: <div />,
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.

I think this should be element:

or Component: SomeComponent. Lowercase component doesn’t look like a valid route object field here.

Assuming we are doing this as a 'don't know don't care' because the location.replace will exit the current frontend anyways?

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.

One of those doesn't really matter, just needs to exist and would get ignored.

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