Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deploy): Release GA - v26.0.0 (electron-updater v6.4.0) #8808

Merged
merged 1 commit into from
Jan 26, 2025

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 26, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

26.0.0

Major Changes

  • #8782 633490cb Thanks @mmaietta! - fix: removing conditional logic that would build HFS+ dmg on non-arm64 macs as HFS+ was sunset in macos 15.2
  • #8582 6a9597b4 Thanks @mmaietta! - chore: remove deprecated fields from winOptions and macOptions. (For winOptions signing configuration, it has been moved to win.signtoolOptions in order to support azureOptions as a separate field and avoid bloating win configuration object. For macOptions, notarize options has been deprecated in favor of env vars for quite some time. Env vars are much more secure)
  • #8572 0dbe357a Thanks @mmaietta! - feat: allowing additional entries in .desktop file, such as [Desktop Actions <actionName>]. Requires changing configuration desktop property to object to be more extensible in the future
  • #8562 b8185d48 Thanks @beyondkmp! - support including node_modules in other subdirectories

Minor Changes

Patch Changes

electron-updater 6.4.0

Minor Changes

Patch Changes

@mmaietta mmaietta changed the title chore(deploy): Release chore(deploy): Release GA - v26.0.0 (electron-updater v6.4.0) Jan 26, 2025
@mmaietta mmaietta merged commit d75d2bf into master Jan 26, 2025
4 checks passed
@mmaietta mmaietta deleted the changeset-release/master branch January 26, 2025 18:00
@MikeMcC399
Copy link

@mmaietta

Could you please clarify the status of release v26.0.0?

In the PR title it is shown as "GA"

On the Releases page it currently shows up as Pre-release

image

$ npm view electron-builder dist-tags
{ latest: '25.1.8', next: '26.0.0' }

Do you plan to make v26.0.0 into the latest release soon? I would really like to use it, but I would prefer to wait if it is not yet ready for production use.

@mmaietta
Copy link
Collaborator

It's under next tag (pre-release) but not on latest yet as we just exited alpha. next means ready for production use though, only alpha isn't. Historically, all releases start as next before graduating to latest after greater user adoption. Do you have a requirement to only use latest tags?

@MikeMcC399
Copy link

@mmaietta

Many thanks for confirming your use of pre-release! I will go ahead and prepare to use it. (No I don't need to have a latest tag assigned.)

I was basing my original understanding on the GitHub Documentation definition of the release term "pre-release":

image

@mmaietta
Copy link
Collaborator

Bah, you're absolutely correct. Based on the GH documentation, I'm misusing the pre-release tag. This is how electron-builder's CD has behaved since I joined years ago, so I never had a reason to change it.
It's kind of ironic though, as I've received more GH issues opened about confusion when it's marked as latest on GH but next on npm, so I default GH releases to say pre-release to reduce confusion.

@MikeMcC399
Copy link

@mmaietta

It sounds like your consistent handling of the pre-release tag together with next is fine and in line with the spirit of GitHub's documentation. Early adopters will use pre-release knowingly at their own risk. Others may decide to wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How to prevent package.json's description from being used as the process name?
2 participants