github actions workflow to publish to npm and then trigger codepipeline to publish to maven/nuget

[chungjac]

Problem

The current publishing process runs everything through CodePipeline with hourly triggers, using classic npm tokens and mixed authentication patterns.

Context: npm has changed granular tokens from unlimited expiration to 90-day max limit: https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/#granular-npm-access-token-lifetime-limits

Solution

Implement a hybrid approach

GitHub Actions handles npm publishing:

• Uses OIDC authentication, eliminating token expiration issues
• Triggered only when commits are merged to main, removing the need for hourly triggers
• Centralizes version management and git operations

CodePipeline continues to handle Maven and NuGet publishing:

• Triggered on-demand by GitHub Actions after npm publishing
• Maintains existing authentication patterns for these package types
• Ensures version consistency across all packages

Benefits:

• Eliminates npm token rotation burden with OIDC authentication
• Reduces resource waste with on-demand execution instead of hourly runs
• Improves security with modern authentication patterns
• Synchronizes versions across all package managers

Note

verison is bumped from 1.0.331 --> 1.0.335 as used a few versions for testing

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.