ci: publish-internal-version-action-workflow

[Zaimwa9]

Thanks for submitting a PR! Please check the boxes below:

• I have read the Contributing Guide.
• I have added information to docs/ if required so people know about the feature.
• I have filled in the "Changes" section below.
• I have filled in the "How did you test this code" section below.

Changes

Contributes to #377

• Created .github/workflows/publish-internal.yml to manual dispatch workflow to publish packages with internal tag (based on publish.yml)

Steps:

1. Bump to a higher version with tag internal (with an increment if multiple releases needed e.g 11.1.0-internal.1)
2. Trigger Publish Internal NPM Package from action
3. Run workflow with selected branch

Usage in app with
npm i flagsmith@11.1.0-internal.1

Bonus

• Added the pull request template

How did you test this code?

• Not yet

[germangarces]

Bump to a higher version with tag internal

Is this prone to failure? Could we document it or get the workflow to do it on its own?

[khvn26]

@germangarces see #379.

[Zaimwa9]

My bad, I forgot we did add release-please and it's taking care of the version bumps now. Only on main though.

I'm exploring the possibilities right now. But as the idea was to not have to merge internal versions into main, the solution might be simpler than I thought and not so "semverically" hideous.

What do you think about:

• Having the workflow suffix the current version with internal.{runNumber} (without merging) -> npm will consider as a distinct version so no conflict
• Testing how much we want the internal version
• Once complete and meant to be merged release please will deal with correct versioning without having a dirty version history

cc @khvn26 i'll close your issue

[germangarces]

LGTM :)