eclipse-openj9 / openj9-website

openj9-website
24 stars 28 forks source link

Bump gatsby-source-wordpress from 3.3.28 to 4.0.8 #293

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 3 years ago

Bumps gatsby-source-wordpress from 3.3.28 to 4.0.8.

Release notes

Sourced from gatsby-source-wordpress's releases.

v3.9 (July 2021 #1)

Welcome to gatsby@3.9.0 release (July 2021 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v3.8 (June 2021 #2)

Welcome to gatsby@3.8.0 release (June 2021 #2)

Key highlights of this release:

Also, check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v3.7 (June 2021 #1)

Welcome to gatsby@3.7.0 release (June 2021 #1)

Key highlights of this release:

... (truncated)

Changelog

Sourced from gatsby-source-wordpress's changelog.

4.0.8 (2021-07-13)

Note: Version bump only for package gatsby-source-wordpress

4.0.7 (2021-07-09)

Bug Fixes

  • gatsby-source-wordpress: Backporting auth leak fix (#32315) (98e726f)

4.0.6 (2021-04-07)

Bug Fixes

4.0.5 (2021-03-08)

Bug Fixes

4.0.4 (2021-03-01)

Bug Fixes

4.0.3 (2021-02-24)

Note: Version bump only for package gatsby-source-wordpress

4.0.2 (2021-02-24)

Note: Version bump only for package gatsby-source-wordpress

4.0.1 (2021-02-05)

Note: Version bump only for package gatsby-source-wordpress

4.0.0 (2021-02-04)

Note: Version bump only for package gatsby-source-wordpress

3.11.0 (2021-02-02)

Note: Version bump only for package gatsby-source-wordpress

3.11.0-next.0 (2021-01-18)

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/eclipse-openj9/openj9-website/network/alerts).
pshipton commented 2 years ago

@doveye what is the process to doing this update? I didn't check thoroughly if there are any vulnerabilities fixed between 3.3.28 to 4.0.8. I'm concerned that if we aren't on the latest version and there is a vulnerability then we'll need to scramble to update.

doveye commented 2 years ago

@pshipton Good question, I don't think there is a process. It looks like this is the first such PR to be created in this repo, and I'm not aware of any updates being made to website levels since the website was created. I guess addressing it would be similar to the docs, ie creating the website locally with updated dependency levels and checking that nothing breaks.

dependabot[bot] commented 1 year ago

Superseded by #350.