It seems there is Travis CI enabled but not used further configured?

https://travis-ci.com/pnpm/spec/builds/73894871

I've noticed that the specifications only exist up to lockfile version 5.2. Are there any details on the specifications for lockfile versions 5.3, 5.4 and 6? Thanks!

Description

Is it possible to add specification for lockfile v9?

Related PRs:

• pnpm/pnpm#7666
• pnpm/pnpm#7861

The existing table that compares pnpm version to lockfile version is nice, but I recently needed a more complete version of this relationship. I had to test it out myself to be sure.

Can we update this table to something like the following?

| pnpm version | generates lockfile | parses lockfiles |
| ------------ | ------------------ | ---------------- |
| 6.x          | 5.3                | 5.3, 5.4         |
| 7.x          | 5.4                | 5.3, 5.4         |
| 8.x          | 6.0, 6.1*          | 6.0, 6.1*        |
| - 8.6.1      | 6.1                | ---              |
| - 8.6.2      | 6.1                | ---              |
| - after      | 6.0                | ---              |
| 9.x          | 9.0                | 6.0*, 7.0, 9.0   |
| - 9.0.0      | 9.0                | 7.0, 9.0         |
| - after      | 9.0                | 6.0, 7.0, 9.0    |

Rendered:

It would have to be expanded to include older pnpm versions.

The asterisks:

• [email protected]
  • lockfile 6.1: pnpm 8.6.1 and 8.6.2 generated lockfile version 6.1, but after that, lockfile verison 6.0 was generated
• [email protected]
  • lockfile 6.0: pnpm 9.0.0 could not parse lockfile version 6.0, but from 9.0.1 onward, it could
  • lockfile 7.0: pnpm 9.0.0-alpha versions generated lockfiles with version 7.0, but the final release of 9.0.0 generated lockfiles with 9.0

I was reading https://github.com/pnpm/spec/blob/master/lockfile/6.0.md and noticed some things:

### lockfileVersion

A [ComVer](https://github.com/staltz/comver) starting with the major number `4`.

### packages

This is a mapping of dependency path to dependency object. The [dependency path](../dependency-path.md) is relative (e.g., `/[email protected]`) if the dependency
is from the registry specified in the registry property, or absolute (e.g., `registry.node-modules.io/[email protected]`) if the package's
registry differs from the one specified as default in the shrinkwrap file.
That should say 6 right?

I think the major version is 6 now, not 4.

Also dependency-path.md describes a format that seems like the one use in v5 lock files, not the one used in v6 lock files. There was a change to the format between v5 and v6 (I see /mime/1.6.0 change to /[email protected] and /webpack-cli/4.10.0_fzn43tb6bdtdxy2s3aqevve2su replaced with /[email protected]([email protected])([email protected])([email protected]) when updating for example). This change does not seem to be documented anywhere that I can find.