[Bug]: Package publishing issue?

[Stanzilla]

CheckList

• I agree to follow this project's Code of Conduct
• I have read and followed the Contributing Guide
• I have read and followed the Issue Tracker Guide
• I have searched and referenced existing issues and discussions
• I am filing a BUG report.
• I have managed to reproduce the bug after upgrading to the latest version
• I have created an accurate and minimal reproduction

Version

6.6.4

In What environments are you experiencing the problem?

Node.js

Node Version (if applicable)

22.14.0

Link To Reproduction

https://www.npmjs.com/package/fabric?activeTab=code

Steps To Reproduce

1. Install fabric from npm
2. Open the package.json

Expected Behavior

master branch should be what is published on npm and/or what is published on npm is the latest version of the code

Actual Behavior

• npm has https://www.npmjs.com/package/fabric version 6.7.0
• github master branch is on version 6.6.2 https://github.com/fabricjs/fabric.js/blob/master/package.json#L5

there is a very important change missing in 6.7.0 that, for some reason, 6.6.2 has which is the bump of the version of canvas in optionalDependencies

6.7.0

"optionalDependencies": {
    "canvas": "^2.11.2",
    "jsdom": "^20.0.1"
  },

6.6.2

"optionalDependencies": {
    "canvas": "^3.1.0",
    "jsdom": "^26.0.0"
  }

other versions are different as well.

Any insight on what is up with that?

Error Message & Stack Trace

[asturur]

Master branch is currently a v7.0 where we didn't bump the version yet.
I should do it to avoid doubts.
The current 6.7.0 is in the 6.x branch.

[Stanzilla]

Master branch is currently a v7.0 where we didn't bump the version yet. I should do it to avoid doubts. The current 6.7.0 is in the 6.x branch.

Oh I see, could we get a 6.x release with the canvas bump then maybe?

[asturur]

What is the canvas bumb? the node-canvas 3.x? that is breaking change so i couldn't publish as 6 because it removes node 16 entirely

[Stanzilla]

What is the canvas bumb? the node-canvas 3.x? that is breaking change so i couldn't publish as 6 because it removes node 16 entirely

Yeah..it causes trouble in CI because of node-gyp stuff. I can force it with a resolution just fine as a workaround though.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Stanzilla]

@asturur is there an ETA for v7 then? Would it be worth releasing it just for the node bump and updated deps?

[asturur]

I have to finish this pr here:
#10587
that i m having difficulties with because is boring, requires a lot of tests and i m not satisfied with the result either.
I miss just that.