merge #166
Open
merge #166
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ci: remove node manifest tests
👷 Deploy request for phileco pending review.Visit the deploys page to approve it
|
fix(deps): upgrade multer
auto-merge was automatically disabled
June 6, 2025 14:18
Head branch was pushed to by a user without write access
* fix: ensure rendering engine has vendored libvips * chore: bump caniuse * test: visit and intercept direct html routes and avoid hitting redirects which mess up html header assertions
auto-merge was automatically disabled
June 23, 2025 18:49
Head branch was pushed to by a user without write access
update documentation for tailwind css
docs: improve intro text in README – first contribution by Soundharyaa Shri Co-authored-by: Philippe Serhal <philippe.serhal@netlify.com>
auto-merge was automatically disabled
August 5, 2025 11:56
Head branch was pushed to by a user without write access
…pes/* deps, handle change in tmp package (#39343) * fix: use forked devcert to avoid pulling transitive deps from its @types/* deps * chore: remove cpy from structured-logging test * chore: remove del-cli from cli test * chore: use gatsbyjs fork and not private one * chore: use @expo/devcert as it is being maintained * fix: create .cache directory before trying to create temp file in it
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
chore: streamline circleci dependencies Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
* fix: correct renovate paths for deprecated packages * chore: update lockfile * chore: remove leftover dead Gatsby Cloud code --------- Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
* chore: simplify Renovate setup * chore: add back postUpdateOptions, disable automerge --------- Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
fix(deps): upgrade socket.io, socket.io-client
* chore: remove AskGatsbyJS Twitter link * Apply suggestion from @serhalp * chore: remove more outdated social refs
* test(gatsby-cli): tolerate varying stack traces * test: import mocked module the same way it's used This mismatch stopped working after node 18. * test: use more specific snapshot for res headers Some of the connection header defaults depend on the node.js major version wip this is a fix for the headers one * test: skip unstable GC tests on node 20+ * test: adjust assertion to work on node 22 locally See inline comment * test: fix sharp build error in lmdb-regeneration fixture The `lmdb-regeneration` integration test fixture had an `.npmrc` file forcing all packages to be built from source, which caused sharp to fail compilation in Node 20+ CircleCI images (Ubuntu Noble) due to... who knows what, honestly. Since this fixture specifically needs lmdb built from source but not sharp (it's testing something specific to this), this replaces the global `.npmrc` `build-from-source` flag with a targeted `postinstall` script that only rebuilds lmdb from source, allowing sharp to use prebuilt binaries. This resolves the "cannot find -l:libvips-cpp.so.42" linker errors that were blocking integration tests on Node 20+ while preserving the fixture's intended lmdb compilation testing. AFAICT this was... basically the only solution. Whew * fix(gatsby): bump `webpack-virtual-modules` to get this bug fix: sysgears/webpack-virtual-modules#172 causing this, unclear when: ``` TypeError: Cannot read properties of null (reading 'fileWatchers') ``` * ci: test against Node 18, 20, 22 - run unit tests against all three - run integration tests against earliest and latest - make sure to separate npm cache by node version * ci: test against node 22.13 to avoid bug for now
- babel-plugin-remove-graphql-queries@5.16.0-next.0 - babel-preset-gatsby-package@3.16.0-next.0 - babel-preset-gatsby@3.16.0-next.0 - create-gatsby@3.16.0-next.0 - gatsby-adapter-netlify@1.4.0-next.0 - gatsby-cli@5.16.0-next.0 - gatsby-codemods@4.16.0-next.0 - gatsby-core-utils@4.16.0-next.0 - gatsby-cypress@3.16.0-next.0 - gatsby-design-tokens@5.16.0-next.0 - gatsby-dev-cli@5.16.0-next.0 - gatsby-graphiql-explorer@3.16.0-next.0 - gatsby-legacy-polyfills@3.16.0-next.0 - gatsby-link@5.16.0-next.0 - gatsby-page-utils@3.16.0-next.0 - gatsby-parcel-config@1.16.0-next.0 - @gatsbyjs/parcel-namer-relative-to-cwd@2.16.0-next.0 - gatsby-plugin-benchmark-reporting@3.16.0-next.0 - gatsby-plugin-canonical-urls@5.16.0-next.0 - gatsby-plugin-catch-links@5.16.0-next.0 - gatsby-plugin-coffeescript@5.16.0-next.0 - gatsby-plugin-cxs@5.16.0-next.0 - gatsby-plugin-emotion@8.16.0-next.0 - gatsby-plugin-facebook-analytics@5.16.0-next.0 - gatsby-plugin-feed@5.16.0-next.0 - gatsby-plugin-flow@4.16.0-next.0 - gatsby-plugin-fullstory@5.16.0-next.0 - gatsby-plugin-google-analytics@5.16.0-next.0 - gatsby-plugin-google-gtag@5.16.0-next.0 - gatsby-plugin-google-tagmanager@5.16.0-next.0 - gatsby-plugin-image@3.16.0-next.0 - gatsby-plugin-jss@5.16.0-next.0 - gatsby-plugin-layout@4.16.0-next.0 - gatsby-plugin-less@7.16.0-next.0 - gatsby-plugin-lodash@6.16.0-next.0 - gatsby-plugin-manifest@5.16.0-next.0 - gatsby-plugin-mdx@5.16.0-next.0 - gatsby-plugin-no-sourcemaps@5.16.0-next.0 - gatsby-plugin-nprogress@5.16.0-next.0 - gatsby-plugin-offline@6.16.0-next.0 - gatsby-plugin-page-creator@5.16.0-next.0 - gatsby-plugin-postcss@6.16.0-next.0 - gatsby-plugin-preact@7.16.0-next.0 - gatsby-plugin-preload-fonts@4.16.0-next.0 - gatsby-plugin-react-css-modules@5.16.0-next.0 - gatsby-plugin-react-helmet@6.16.0-next.0 - gatsby-plugin-sass@6.16.0-next.0 - gatsby-plugin-schema-snapshot@4.16.0-next.0 - gatsby-plugin-sharp@5.16.0-next.0 - gatsby-plugin-sitemap@6.16.0-next.0 - gatsby-plugin-styled-components@6.16.0-next.0 - gatsby-plugin-styled-jsx@6.16.0-next.0 - gatsby-plugin-styletron@8.16.0-next.0 - gatsby-plugin-stylus@5.16.0-next.0 - gatsby-plugin-subfont@5.16.0-next.0 - gatsby-plugin-twitter@5.16.0-next.0 - gatsby-plugin-typescript@5.16.0-next.0 - gatsby-plugin-typography@5.16.0-next.0 - gatsby-plugin-utils@4.16.0-next.0 - gatsby-react-router-scroll@6.16.0-next.0 - gatsby-remark-autolink-headers@6.16.0-next.0 - gatsby-remark-code-repls@7.16.0-next.0 - gatsby-remark-copy-linked-files@6.16.0-next.0 - gatsby-remark-custom-blocks@5.16.0-next.0 - gatsby-remark-embed-snippet@8.16.0-next.0 - gatsby-remark-graphviz@5.16.0-next.0 - gatsby-remark-images-contentful@6.16.0-next.0 - gatsby-remark-images@7.16.0-next.0 - gatsby-remark-katex@7.16.0-next.0 - gatsby-remark-prismjs@7.16.0-next.0 - gatsby-remark-responsive-iframe@6.16.0-next.0 - gatsby-remark-smartypants@6.16.0-next.0 - gatsby-script@2.16.0-next.0 - gatsby-sharp@1.16.0-next.0 - gatsby-source-contentful@8.17.0-next.0 - gatsby-source-drupal@6.16.0-next.0 - gatsby-source-faker@5.16.0-next.0 - gatsby-source-filesystem@5.16.0-next.0 - gatsby-source-graphql@5.16.0-next.0 - gatsby-source-hacker-news@5.16.0-next.0 - gatsby-source-lever@5.16.0-next.0 - gatsby-source-medium@5.16.0-next.0 - gatsby-source-mongodb@5.16.0-next.0 - gatsby-source-npm-package-search@5.16.0-next.0 - gatsby-source-shopify@10.1.0-next.0 - gatsby-source-wikipedia@5.16.0-next.0 - gatsby-source-wordpress@7.17.0-next.0 - gatsby-transformer-asciidoc@4.16.0-next.0 - gatsby-transformer-csv@5.16.0-next.0 - gatsby-transformer-documentationjs@7.16.0-next.0 - gatsby-transformer-excel@5.16.0-next.0 - gatsby-transformer-hjson@5.16.0-next.0 - gatsby-transformer-javascript-frontmatter@5.16.0-next.0 - gatsby-transformer-json@5.16.0-next.0 - gatsby-transformer-pdf@4.16.0-next.0 - gatsby-transformer-react-docgen@8.16.0-next.0 - gatsby-transformer-remark@6.16.0-next.0 - gatsby-transformer-screenshot@5.16.0-next.0 - gatsby-transformer-sharp@5.16.0-next.0 - gatsby-transformer-sqip@5.16.0-next.0 - gatsby-transformer-toml@5.16.0-next.0 - gatsby-transformer-xml@5.16.0-next.0 - gatsby-transformer-yaml@5.16.0-next.0 - gatsby-worker@2.16.0-next.0 - gatsby@5.16.0-next.0
auto-merge was automatically disabled
August 27, 2025 12:52
Head branch was pushed to by a user without write access
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Documentation
Tests
Related Issues