Repository navigation
Release 1.1.1 - #46
Merged
Merged
Conversation
Merge master (v1.1.0) into develop
For a package in a subdirectory, such as ReleaseFlow, the messages named CHANGELOG.md at the repository's root, which doesn't exist.
GitHub resolves every action of a job before it runs, even one whose step is skipped, so Self: Register failed where 1.1.0 merged: its job named BioJulia/Workflows@v1.1.0, which only exists once it's registered. release.yml and register.yml now run the action at its release, or with local-action at the checkout, in two jobs, one of which is skipped. The tokens move to a job that runs neither: release.yml's Push job applies the changes that its Prepare job passes on, and register.yml's Register job comments.
…lues The summary listed only the line naming each failing test's file, so a failure such as 1.1.0's reworded message didn't say what the test expected. It now shows each failure up to its stack trace, with paths relative to the repository.
The pinned and the local action's steps shared the ids prepare and registration since they moved into jobs of their own, so a step's id no longer named one step of the workflow, and the last release's tests, which find the local steps as prepare-local and registration-local, failed in the breaking check though the workflows' inputs and outputs are unchanged. Each action step's id is now its job's key.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This prepares the release 1.1.1: its version in Project.toml, its section of the changelog, with its links, and its pins.
Changed
Fixed
ReleaseFlow/CHANGELOG.mdfor a package in a subdirectory, rather thanCHANGELOG.md.release.ymlandregister.ymlrun the action at its release, and withlocal-actionat the checkout, in jobs of their own, since GitHub resolves every action of a job before it runs, even one whose step is skipped; soSelf-Register.ymlno longer fails where a release merges, whose own tag doesn't exist until it's registered. The jobs that run the action no longer have the tokens:release.yml'sPushjob applies the changes that itsPreparejob passes on, and pushes them, andregister.yml'sRegisterjob, after itsRegistrationjob, comments, and only runs where there's a version to register.