James Sumners

chore: merge next into main for v5 release

12

For the same reasoning as given in https://github.com/pinojs/pino/pull/1947#issue-2260133148, we should just get v5 released. ***Important:*** once this PR is merged in: 1. We need to create a 4.x branch (actually,...

Cut new version from the next branch.

Cut new version from the `next` branch.

Cut new version from the `next` branch. Relied upon by: + [ ] `pino-http`

I had to write the following test application to determine if my desired use case would work. I couldn't find it in the documentation or tests. Specifically, I needed to...

The test suite should be converted to [tap](https://node-tap.org/) to be consistent with other organization modules.

Set.prototype.at

16

```js const aSet = new Set([1, 2, 3, 4]) console.log(aSet.at(1)) // 2 // Would be _really_ nice: console.log(aSet[1]) // 2 ```

The `next` branch should be ready for issuing a release to coincide with `fastify@5`.

Let's say your project is in "/home/foouser/Programming Projects/fooproject/". When executing `giternal update` from that directory, you'd get the error: "sh: line 0: cd: /home/foouser/Programming: No such file or directory ..updated"

Python 3.8 changes how the `collections` package works. See https://stackoverflow.com/questions/53978542/how-to-use-collections-abc-from-both-python-3-8-and-python-2-7 Not that this will ever get merged, of course. FWIW, this branch is based on #65.