- Upgraded to
covector@0.12.4
294a3c0
(#354 by @jbolda) The action now supports running in dry run mode. This enables testing of workflows and publish sequences prior to publishing.
9f85eae
(#355 by @jbolda) The URL to create a change file on forks was broken. It was incorrectly pointing at the root repo.e81201f
(#350 by @chippers) Fix GitHub pull request comment link to correctly point at the docs.
- Upgraded to
covector@0.12.3
- Upgraded to
covector@0.12.2
055a319
(#343 by @jbolda) Missed some logger function which were improperly passed an non-message object. If rendering an object, it requiresmsg
andrenderAsYAML
.
- Upgraded to
covector@0.12.1
e5d2be5
(#322 by @echocaro) On comment post error, upload the content instead as an artifact. This prevents the workflow from failing on a fork, and allows another workflow with permissions to handle the work from there.
c78050e
(#324 by @jbolda) Handleworkflow_run
to enable generating a comment, uploading it as an artifact and post the comment in a workflow which has appropriate permissions.
e2c83dc
(#318 by @jbolda) Addexports
topackage.json
for improved capability and an enhanced experience when developed covector and testing locally.dda5430
(#337 by @jbolda) When there are no changes, also include a link to create a new change file.c72c060
(#316 by @jbolda) Use node v20 in GitHub Action.ce43ad7
(#319 by @jbolda) Add logger instance to allow custom loggers based on the usage context. It enables different structured logs for the CLI vs within a GitHub Action, as well as for local development and testing.
- Upgraded to
covector@0.12.0
ce43ad7
(#319 by @jbolda) Switch to Vitest for the test runner. This improves speed and enables improved ability to update to current standards. Additionally, we usepino-test
with the changes to the logger to more specifically check log output. Along with this, we switch multiple test fixtures to run commands that would return more standard output across OS which reduces test flakiness.
9480736
(#299 by @jbolda) Return additionalstatus
content fromcovector
to enable posting a comment in PR providing additional context of the expected change files.9202dca
(#307 by @jbolda) PasscreateContext
function from action through to changelog to enable passing specific context usable within changelogs.9480736
(#299 by @jbolda) Add option to post a comment in a GitHub pull request comment lifting the context from covector.2db4d6e
(#309 by @jbolda) The GitHub comment was previously rather terse. We are now including the sha within the comment so as to make it clear when the command last ran.9202dca
(#307 by @jbolda) Query the GitHub API for the PR creator, and highlight their names in the changelogs for recognition of their contribution.737ebed
(#310 by @jbolda) Fix links within GitHub by removing the explicit markdown syntax to allow GitHub Flavored Markdown to resolve, render and interlink the Version Packages PR with the change files and their PRs.
- Upgraded to
covector@0.11.0
- Upgraded to
covector@0.10.2
- Upgraded to
covector@0.10.1
- Upgraded to
covector@0.10.0
7b6201c
(#264) Bump Typescript to v4.9, and deeply update types in the lower level functions to start.
- Run the Github Action with Node v16. The previous version, Node v12, will no longer be supported.
- Update
@actions/core
and@actions/github
to remove deprecation warnings. - Update multiple devDeps, semver, yargs, inquirer, and packages in our action. This is primarily internal upgrades and don't affect external APIs.
- Remove the
to-vfile
package as a dependency. This allows us to focus our file reference to our specific needs, and one less dependency to maintain. With this change, we also converted a handful of promises into generators for better compatibility and control with effection. - Set the
target_commitish
field on created releases. - Upgrade to
effection
v2. This is primarily an internal improvement, but will enable future features such as fetching from an endpoint to check if a version of a package was published. It also brings an updated dependency to gracefully shutdown windows processes.
- The action created a release for any
publish
keys inpkgManger
, but didn't do it for anything specified inpackages
. This meant that if you elected not to usepkgManager
, it would not create a release. This has been fixed and it will now create a release. We also added some debug output to improve the debugging experience. - Include information about the created release in the actions outputs
- Preview version template overwrites the prerelease identifier
- The ability to adjust the Github Release git tag was previously added, and the fallback used only worked for JavaScript packages. This fix uses the package nickname instead which will work for any package manager.
- Adds the ability to update a Github Release if it exists and is a draft, or create it if it doesn't yet exist.
- Allow one to specify the
releaseTag
that determines the Github Release tag used. This also let's you specifyfalse
to explicitly skip creating a Github Release for the package. resolves #203, resolves #204.
- Adjust output from assemble and covector to expose the template that is piped into each command. This allows us to set it as an output in the github action.
- The
status
command did not previously have any output to act on. Add a new output that contains the covector output. - Bump
@effection/node
which fixes and now supports node 16 on Windows. (Other platforms had full support.) - This switches to using Typescript project references to build (previously rollup). It should affect the underlying packages or use.
- Pass head branch name into covector for running preview in action Tag gets piped into template in assemble Fix published boolean bug in command
- Add preview command for versioning and publishing preview packages
- Action generates pull request comments when it runs
covector preview
- Mock out full Github Release flow to help in testing the Github Action. Adjust command pipe to function to fix
undefined
being piped to Github Release body.
- Pipe the previous command output into function commands. This is primarily for the Github Releases which injects functions and will need the changelog output from
pkgCommandsRan
.
- The action
dist
folder was accidentally gitignored. We want to commit it so actions can run directly from the dist without install.
- Fix
init
Rust based packages coming in as undefined.
- The result of the action had the covector output scoped, and further on logs failed. Hoist it so it is in the correct scope.
- The
core
method was not passed to the release util in the Github Action. This failed the Github Release creation.
- Switch to currying github context as binding returned undefined.
- Add extra outputs for which packages published and a list of packages. This is useful for chaining runs of the action together.
- Some workflows require different actions for different packages. Most of this can be codified into config. However there are cases where you may need to run a command for a dynamic set of packages.
- Add
modifyConfig
property that takes a function which can modify the config file that is loaded. This will likely only be used in the Github Action to inject a JavaScript function into the publish sequences which creates a Github Release.
- The command sequence was piping to the return correctly, but in publish, we didn't properly concat the text. Fix that.
- Add extra outputs that says which command was run (for
version-or-publish
) and if something was published.
- Increase default timeout and allow it to be set from config.
Bumped due to dependency.
- Fix create release and upload errors on publish.
Bumped due to dependency.
- In --dry-run mode, output the expected commands with data piped in.
- Shift getPublishedVersion check prior to commands running. Without this, postpublished would never run (since packages were just published and are update to date).
- Added new dryRunCommand to specify a different command to run instead in --dry-run mode instead of skipping the specified command.
- Change files were being deleted too quickly for git info to be retrieved. Shift to end of sequence.
- Pull and set git meta information on change files as an array of commits. This can then be piped into changelogs.
- Allow complex commands specified as an object. This let's one specify a dryRunCommand that is executed in --dry-run mode instead (so no accidental publishes!) or to set pipe to true that the output is returned from the main covector function. The pipe likely won't be used directly, but can be consumed within the action to create a Github Release, etc.
- Version commands used to only run on changes, but ignore parents. Reconfigure that we resolve the parents and run commands on both direct changes and changes through a dependency.
- Adjust covector publish command to return the pkg as part of the out.
- Split out child_process commands into separate package.
Bumped due to dependency.
Bumped due to dependency.
Bumped due to dependency.
Bumped due to dependency.