VOTE: Release JHipster 9.1.0

10 views
Skip to first unread message

Matt Raible

unread,
May 23, 2026, 1:14:14 PMMay 23
to JHipster dev team

Hello team,


I propose we release JHipster 9.1.0 based on the code that is currently in the main branch, along with any subsequent updates, before the release starts. 


Please vote in the next 48 hours to approve this release. I plan to do the release on Tuesday evening (Denver time).


+1 to release

-1 not to release (with reasons)

0 watching, but don’t care


We need three +1 votes to proceed with the release. Any -1 votes will cancel the release. 


You can see the current draft of the release notes at https://github.com/jhipster/generator-jhipster/releases.


Please use the 9.1.0 milestone if you’d like to add additional issues to this release, or comment on this issue:


https://github.com/jhipster/generator-jhipster/issues/33521


Thanks,


Matt

Frederik Hahne

unread,
May 23, 2026, 1:22:50 PMMay 23
to Matt Raible, JHipster dev team
+1

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CAFhCnT4g_HWz2JzQpWysSThYkL%3D5C526D474zgq%3DHOaUx7S5uQ%40mail.gmail.com.

quentin.monmert

unread,
May 23, 2026, 1:32:05 PMMay 23
to JHipster dev team
+1

Daniel Franco

unread,
May 23, 2026, 2:10:03 PMMay 23
to Matt Raible, JHipster dev team
+1

--

Anthony Viard

unread,
May 23, 2026, 2:38:54 PMMay 23
to Daniel Franco, Matt Raible, JHipster dev team
+1
Envoyé de mon iPhone

Le 23 mai 2026 à 20:10, Daniel Franco <dandr...@gmail.com> a écrit :



Charlie Mordant

unread,
May 24, 2026, 4:09:00 PMMay 24
to Anthony Viard, Daniel Franco, Matt Raible, JHipster dev team
+1

To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/F0E98E82-4BE6-4E5F-87DA-09864E25265B%40gmail.com.


--
Charlie Mordant

Matt Raible

unread,
May 26, 2026, 9:43:50 PMMay 26
to Charlie Mordant, Anthony Viard, Daniel Franco, JHipster dev team
The vote passes with 5 +1s and 0 -1s. I'll start the release in 30 minutes.

On May 24, 2026, at 14:08, Charlie Mordant <cmor...@gmail.com> wrote:



Matt Raible

unread,
May 27, 2026, 12:52:36 PMMay 27
to Charlie Mordant, Anthony Viard, Daniel Franco, JHipster dev team
It seems npmjs.com might’ve changed permissions because I’m not longer able to publish generator-jhipster. I’ve generated a new token twice (once with R/W for @jhipster and once with R/@ for generator-jhipster). 

I believe an existing owner has to add my npm user as an owner for the package:

> npm owner add mraible generator-jhipster

From what I can tell, this command must be run by jdubois or deepu105. 

Thanks!

Matt

Anthony Viard

unread,
May 27, 2026, 1:00:23 PMMay 27
to Matt Raible, Charlie Mordant, Daniel Franco, JHipster dev team
Hi Matt,
I’ve seen they enforce or change the rules to publish packages in npmjs after multiple supply chain attacks. 

I use trusted GitHub repositories to deploy from GH to my npm repositories, it may be used for org repo too (Inside a publish job, no token required). 

Cheers,

Anthony 
Envoyé de mon iPhone

Le 27 mai 2026 à 18:52, Matt Raible <ma...@raibledesigns.com> a écrit :

It seems npmjs.com might’ve changed permissions because I’m not longer able to publish generator-jhipster. I’ve generated a new token twice (once with R/W for @jhipster and once with R/@ for generator-jhipster). 

Matt Raible

unread,
May 27, 2026, 1:05:38 PMMay 27
to Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
Hi Anthony,

That’s good to know. I think these recent changes now require me to be an owner. 

I’m using the jhipster-ansible project to do the release with the following command:

ansible-playbook -v playbooks/generator-jhipster-release.yml -e "release_type=9.1.0”

I don’t really want to change this workflow in the middle of a release. 

At my company, we use a workflow like the one you’re talking about. It leverages OIDC and doesn’t read any tokens from the environment. 


I believe someone has to set us up as a trusted publisher for this to work. https://docs.npmjs.com/trusted-publishers

Thanks,

Matt

Julien Dubois

unread,
May 27, 2026, 1:07:35 PMMay 27
to Anthony Viard, Matt Raible, Charlie Mordant, Daniel Franco, JHipster dev team
So that’s my fault, with the security issue we had a few weeks ago, I limited the access:

-> Matt you should have the permissions now

The only issue I have is with generator-jhipster-entity-audit, it seems there’s an error on the npmjs side, then I don’t think we use it anymore.

There are better ways to do this, I’ve configured it recently for jhipster-react, with OIDC support to allow publishing only from GitHub. We may have a look, but at least Matt you are now unblocked.

Matt Raible

unread,
May 27, 2026, 1:12:43 PMMay 27
to Julien Dubois, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
It still doesn’t work. The following command only shows you and Deepu:

npm owner ls generator-jhipster

If you think it’s not necessary for me to be an owner, do I need to generate another access token?

Thanks,

Matt

Julien Dubois

unread,
May 27, 2026, 1:18:30 PMMay 27
to Matt Raible, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
The owner tag shouldn’t give you more permissions, here I’m sure you have read and write access on generator-jhipster. Can you try with a new token?

Matt Raible

unread,
May 27, 2026, 1:22:41 PMMay 27
to Julien Dubois, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
I created a new token with R/W for generator-jhipster. It still doesn’t work:

"npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access", "npm error code E403", "npm error 403 403 Forbidden - PUT https://registry.npmjs.org/generator-jhipster - You do not have permission to publish \"generator-jhipster\". Are you logged in as the correct user?", "npm error 403 In most cases, you or one of your dependencies are requesting", "npm error 403 a package version that is forbidden by your security policy, or", "npm error 403 on a server you do not have access to.", "npm error A complete log of this run can be found in: /Users/mraible/.npm/_logs/2026-05-27T17_21_05_301Z-debug-0.log"]

Julien Dubois

unread,
May 27, 2026, 1:51:15 PMMay 27
to Matt Raible, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
I really don’t know what to do… I’ll ping you on a secure channel and give you one of my tokens.

Julien Dubois

Matt Raible

unread,
May 27, 2026, 2:01:47 PMMay 27
to Julien Dubois, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
I tried it again and it worked this time!

Julien Dubois

unread,
May 27, 2026, 2:08:25 PMMay 27
to Matt Raible, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
Awesome !!! There might be a delay, weird…


Julien Dubois

Matt Raible

unread,
May 27, 2026, 2:12:51 PMMay 27
to Julien Dubois, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
Running "npm owner ls generator-jhipster” shows me as an owner now. It didn’t before. I think that was the necessary change, but I’m not certain. 

Matt Raible

unread,
May 27, 2026, 2:40:13 PMMay 27
to Julien Dubois, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
It looks like there’s a license/cla check on jhipster-online that is pending and doesn’t resolve. I’m not prompted to sign a CLA. I am able to override and merge, but it seems like something we should fix. 

Matt Raible

unread,
May 27, 2026, 3:27:19 PMMay 27
to Julien Dubois, Anthony Viard, Charlie Mordant, Daniel Franco, JHipster dev team
The jhipster-online project fails to deploy because of the Maven enforcer rule:

> You are running an incompatible version of Java. JHipster supports JDK 8 to 13.

It’s strange that I didn’t see this with JHipster 9.0.0. Here’s a fix that I’ll merge shortly:


I also promoted the release on socials:

Reply all
Reply to author
Forward
0 new messages