Publishing of the common.js package has been switched off due to
problems with package versioning. Below configuration can succesfully
publish the package, but commiting of the information about bumped-up
version to the Git repository doesn't work - commiter's user name and
e-mail are required. Without this update of the version info, next runs
of the common-js-publish generate the same version of package as
before, and upload is not accepted. We may want to resolve that in the
future.
Possible approaches:
swithing off git versionning (--no-git-tag-version) and creation of
action that checks the newest version of the common.js in the npm
registry and bumps the version up accordingly
adding step that sets user.email and user.name global configs
before execution of the step publishing the package
setting the EMAIL, GIT_AUTHOR_NAME, GIT_COMMITTER_NAME
environment variables before execution of the step publishing the
package
Publishing of the common.js package has been switched off due to problems with package versioning. Below configuration can succesfully publish the package, but commiting of the information about bumped-up version to the Git repository doesn't work - commiter's user name and e-mail are required. Without this update of the version info, next runs of the common-js-publish generate the same version of package as before, and upload is not accepted. We may want to resolve that in the future.
Possible approaches:
--no-git-tag-version) and creation of action that checks the newest version of the common.js in the npm registry and bumps the version up accordinglyuser.emailanduser.nameglobal configs before execution of the step publishing the packageEMAIL,GIT_AUTHOR_NAME,GIT_COMMITTER_NAMEenvironment variables before execution of the step publishing the package