π¦ Update invite packages (major)
This PR contains the following updates:
See all other Renovate PRs on the Dependency Dashboard
Release Notes
GoogleCloudPlatform/functions-framework-nodejs (@βgoogle-cloud/functions-framework)
v4.0.0
β BREAKING CHANGES
- upgrade all dependencies
- delete the undocumented "typed" function signature
- drop support for old nodejs versions
Bug Fixes
- delete the undocumented "typed" function signature (c0714e7)
Miscellaneous Chores
v3.5.1
Bug Fixes
- correct handling of IGNORED_ROUTES set to empty (4799207)
v3.5.0
Features
- adds a new ignored-routes config option (70f68e9)
Bug Fixes
- deps: downgrade @βtypes/express to v4 (d40a514)
v3.4.6
Bug Fixes
v3.4.5
Bug Fixes
v3.4.4
Bug Fixes
v3.4.3
Bug Fixes
octokit/rest.js (@βoctokit/rest)
v22.0.0
Bug Fixes
BREAKING CHANGES
- deps: Drop support for NodeJS v18
- deps: Remove deprecated Projects endpoints
- deps: Remove deprecated Copilot usage metrics endpoints
v21.1.1
Bug Fixes
v21.1.0
Features
v21.0.2
Bug Fixes
v21.0.1
Bug Fixes
v21.0.0
Features
BREAKING CHANGES
- package is now ESM
v20.1.2
Bug Fixes
motdotla/dotenv (dotenv)
v17.2.1
Changed
- Fix clickable tip links by removing parentheses (#β897)
v17.2.0
Added
- Optionally specify
DOTENV_CONFIG_QUIET=truein your environment or.envfile to quiet the runtime log (#β889) - Just like dotenv any
DOTENV_CONFIG_environment variables take precedence over any code set options like({quiet: false})
v17.1.0
Added
- Add additional security and configuration tips to the runtime log (#β884)
- Dim the tips text from the main injection information text
const TIPS = [
'π encrypt with dotenvx: https://dotenvx.com',
'π prevent committing .env to code: https://dotenvx.com/precommit',
'π prevent building .env in docker: https://dotenvx.com/prebuild',
'π οΈ run anywhere with `dotenvx run -- yourcommand`',
'βοΈ specify custom .env file path with { path: \'/custom/path/.env\' }',
'βοΈ enable debug logging with { debug: true }',
'βοΈ override existing env vars with { override: true }',
'βοΈ suppress all logs with { quiet: true }',
'βοΈ write to custom object with { processEnv: myObject }',
'βοΈ load multiple .env files with { path: [\'.env.local\', \'.env\'] }'
]
v17.0.1
Changed
- Patched injected log to count only populated/set keys to process.env (#β879)
v17.0.0
Changed
- Default
quietto false - informational (file and keys count) runtime log message shows by default (#β875)
v16.6.1
Changed
- Default
quietto true β hiding the runtime log message (#β874) - NOTICE: 17.0.0 will be released with quiet defaulting to false. Use
config({ quiet: true })to suppress. - And check out the new dotenvx. As coding workflows evolve and agents increasingly handle secrets, encrypted .env files offer a much safer way to deploy both agents and code together with secure secrets. Simply switch
require('dotenv').config()forrequire('@​dotenvx/dotenvx').config().
v16.6.0
Added
- Default log helpful message
[[email protected]] injecting env (1) from .env(#β870) - Use
{ quiet: true }to suppress - Aligns dotenv more closely with dotenvx.
v16.5.0
Added
- π Added new sponsor Graphite - the AI developer productivity platform helping teams on GitHub ship higher quality software, faster.
[!TIP] Become a sponsor
The dotenvx README is viewed thousands of times DAILY on GitHub and NPM. Sponsoring dotenv is a great way to get in front of developers and give back to the developer community at the same time.
Changed
- Remove
_logmethod. Use_debug#β862
jestjs/jest (jest)
v30.1.1
Fixes
-
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#β15800)
v30.1.0
v30.0.5
v30.0.4
Features
-
[expect]TheInversetype is now exported (#β15714) -
[expect]feat: supportasync functionsintoBe(#β15704)
Fixes
-
[jest]jest --onlyFailures --listTests now correctly lists only failed tests (#β15700) -
[jest-snapshot]Handle line endings in snapshots (#β15708)
v30.0.3
Fixes
-
[jest-config]Fix ESM TS config loading in a CJS project (#β15694)
Features
-
[jest-diff]Show non-printable control characters to diffs (#β15696)
v30.0.2
v30.0.1
v30.0.0
probot/probot (probot)
v14.0.2
Bug Fixes
- deps: update @βprobot/octokit-plugin-config (6f2d021)
v14.0.1
Bug Fixes
v14.0.0
BREAKING CHANGES
- Probot is now an ESM only library
- drop Node > 20.17 and Node 21 support
- Switch to GitHub's OpenAPI specification for Webhooks (from
@octokit/webhooksv13) - Remove legacy REST enpoint method access. Users will now have to use the
octokit.rest.*methods - Remove express server from within Probot.
- All properties marked as
privatein Typescript, includingProbot#state, are now private class fields. -
createNodeMiddleware()is now an async function -
@sentry/nodeneeds to be installed separately if needed -
ioredisneeds to be installed separately if needed - The built-in server now listens on
localhostby default instead of0.0.0.0.
Probot v14 Migration Guide
ESM Only Package
Probot is now exclusively an ESM package. Either migrate to ESM (recommended), or use `require(esm).
Migrating to ESM:
- Update
package.json:
{
"type": "module"
}
- Replace all CommonJS
require()statements with ESMimportsyntax - Update your TypeScript configuration:
{
"compilerOptions": {
"module": "node16",
"moduleResolution": "node16"
}
}
For require(esm):
- For TypeScript 5.7-5.8: Use
"module": "nodenext"and"moduleResolution": "nodenext" - For TypeScript 5.9+: Use
"module": "node20"and"moduleResolution": "node20"
Node.js Version Requirements
- Minimum supported version: Node.js 20.18+ and 22+
- Node.js 21 support has been dropped
Webhook Type Definitions
Replace webhook type imports:
// Before
import { WebhookEvent } from "@​octokit/webhooks-types";
// After
import { WebhookEvent } from "@​octokit/openapi-webhooks-types-migration";
REST API Access Pattern
Legacy endpoint methods have been removed:
app.on("issues.opened", async (context) => {
// Before
// const issue = await context.octokit.issues.get(context.issue());
// After
const issue = await context.octokit.rest.issues.get(context.issue());
});
Express Server Removal
The built-in Express server has been removed. To use Express:
- Install Express:
npm install express
- Update your Probot setup:
import Express from "express";
import { createNodeMiddleware, createProbot } from "probot";
const express = Express();
const app = (probot) => {
probot.on("push", async () => {
probot.log.info("Push event received");
});
};
const middleware = await createNodeMiddleware(app, {
webhooksPath: "/api/github/webhooks",
probot: createProbot({
env: {
APP_ID,
PRIVATE_KEY,
WEBHOOK_SECRET,
},
}),
});
express.use(middleware);
express.use(Express.json());
express.get("/custom-route", (req, res) => {
res.json({ status: "ok" });
});
express.listen(3000, () => {
console.log(`Server is running at http://localhost:3000`);
});
HTTP Server no longer listens on 0.0.0.0 by default
The built-in HTTP server will now listen on localhost by default, instead of listening on all available interfaces.
If you wish to change this behaviour, you can use the HOST environment variable, or the --host variable for the probot run command.
env HOST=0.0.0.0 <start script>
probot run --host=0.0.0.0 app.js
Asynchronous Middleware Initialization
createNodeMiddleware() is now asynchronous:
import { createNodeMiddleware } from "probot";
import app from "../app.js";
// Before
// const middleware = createNodeMiddleware(app);
// After
const middleware = await createNodeMiddleware(app);
v13.4.7
Bug Fixes
- update
@octokit/webhooks, remove internalrebindLog()function (#β2220) (c4c67c3), closes #β2062
v13.4.6
Bug Fixes
- update @βoctokit/auth-app and @βoctokit/core to fix logger binding issues (058878b)
v13.4.5
Bug Fixes
v13.4.4
Bug Fixes
- deps: update Octokit dependencies that have ReDos vulnerability (816f2f7)
v13.4.3
Bug Fixes
- deps: update dependency @βprobot/pino to v3 (#β2140) (7c3a99d)
v13.4.2
Bug Fixes
v13.4.1
Bug Fixes
v13.4.0
Features
v13.3.10
Bug Fixes
v13.3.9
Bug Fixes
v13.3.8
Bug Fixes
v13.3.7
Bug Fixes
v13.3.6
Bug Fixes
v13.3.5
Bug Fixes
v13.3.4
Bug Fixes
v13.3.0
Features
- set
x-github-deliveryheader toevent.idfor all requests sent fromcontext.octokitin event handlers (#β2027) (12944d5)
v13.2.2
Bug Fixes
v13.2.1
Bug Fixes
v13.2.0
Features
v13.1.2
Bug Fixes
- deps: update dependency express to v4.19.2 [security] (b1d3ac3)
v13.1.1
Bug Fixes
v13.1.0
Features
v13.0.2
Bug Fixes
- deps: update dependency commander to v12 (737835f)
v13.0.1
Bug Fixes
v13.0.0
Features
BREAKING CHANGES
- Drop support for NodeJS < 18
- replaceΒ
node-fetchΒ with the Fetch API - default
webhookPathis nowΒ/api/github/webhooks -
probot receiveΒ now only supports payloads in JSON format, previously also (unintionally) allowed JS. - Probot now requires that payloads be passed as
stringto the.verify(),.verifyAndReceive()methods. Passing objects is no longer supported - The middleware no longer accepts parsed payloads. You will have to pass it as a string
Note on Vercel deployments:
Set NODEJS_HELPERS environment variable to 0 in order to prevent Vercel from parsing the response body.
See Disable Helpers for detail.
Configuration
π Schedule: Branch creation - "after 12am every weekday" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
π¦ Automerge: Enabled.
β» Rebasing: Never, or you tick the rebase/retry checkbox.
π» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
β οΈ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
β» Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: invite/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jest
npm error dev jest@"30.1.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^29.0.0" from [email protected]
npm error node_modules/ts-jest
npm error dev ts-jest@"29.2.5" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jest
npm error peer jest@"^29.0.0" from [email protected]
npm error node_modules/ts-jest
npm error dev ts-jest@"29.2.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-08-28T19_01_07_264Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-28T19_01_07_264Z-debug-0.log