Status of unreleased commits from nodejs-storage after its archival?

[7hokerz]

I've noticed that nodejs-storage has been archived and moved to the handwritten section of the google-cloud-node monorepo.
Could you clarify how future releases and updates will be managed under this new structure?
My PR was merged before the repository was archived, but it hasn't been included in any official release yet (like v7.19.1).
I'm concerned that my changes are currently 'stuck' between the two states. Could you let me know how these pending updates will be released?

[7hokerz]

@pearigee @codyoss Could you please take a look when you have a moment?

[codyoss]

I can see your commit here: dfca9d9

So if it has not been released it should still be in the next release. Hope that helps!

[7hokerz]

I can see your commit here: dfca9d9

So if it has not been released it should still be in the next release. Hope that helps!

Thank you for your reply! @codyoss
I am already aware of what you mentioned.
However, the reason I asked was that the release of that library is necessary to contribute unimplemented features found in other libraries.
I hope the next release comes out soon!

[shreyanshjain1]

From the way you described it, I’d expect the important distinction now to be:

• the old nodejs-storage repo being archived
• vs the package now being released from the google-cloud-node monorepo workflow

So if your PR was merged before archival but never made it into a published package release, I wouldnt assume it is lost — more likely it now depends on whether that change was carried into the monorepo branch / release pipeline that owns the package going forward.

In other words, the code may be merged historically, but until it gets included in the release path that now publishes @google-cloud/storage, it can still feel “stuck” from a package-consumer point of view.

So I think the real maintainer-side question is probly:

• was that merged change already ported/synced into the monorepo package source?
• and if yes, in which upcoming package release will it ship?

If not, then the practical next step would probly be to identify the exact merged PR/commit and confirm whether it was transferred into the handwritten monorepo location after the archive move.

So I’d guess this is less “the change disappeared” and more “the release ownership moved, and it needs confirmation that the merged commit made it into the new release pipeline.”