@Robert Bradshaw -- this seems sensible. I don't
have the relevant NPM credentials, so am unable to address myself.
Having manual steps in the release process, and esp. not keeping all SDKs
up-to-date seems worth addressing.
On Wed, Apr 17, 2024 at 8:29 AM Danny McCormick
wrote:
> Probably
Probably the easiest way for this to happen is for @Robert Bradshaw
to get the token set up as a secret (should be quick)
and then Austin to take the workflow forward.
In the past to get secrets added, Infra has asked that I (a) email
r...@apache.org with the secret name and secret contents, and
I don't mind doing, esp. if nobody is eager to handle/prioritize the push
artifact in near-term. If I'm to do, let's connect off-list for
token/creds.
Furthermore, I agree that getting RCs as part of the overall
release/validation process would be a nice addition.
On Tue, Apr 16, 2024 at 2:43
Correct, I've just been pushing these manually, and lately there haven't
been many changes to push. I'm all for getting these set up as part of the
standard release process.
On Tue, Apr 16, 2024 at 1:22 PM Danny McCormick
wrote:
> I've never published npm artifacts before, but I imagine the
I've never published npm artifacts before, but I imagine the hardest part
is getting the credentials set up, then it is probably very easy to set up
a GitHub Actions workflow to publish
Hi Beam Devs,
Calling out it looks like our release process for apache-beam for
typescript/npm is broken, seemingly the last published release was 2.49.0
about 9 months ago. The other languages look like they are publishing to
expected locations.
https://www.npmjs.com/package/apache-beam
I
