Release 1.0.2 #39
Merged
Release 1.0.2 #39
Conversation
This file contains 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 will release 1.0.2, which contains the new
ci_validate_hub_config()function and does the following:Next steps
validate-configaction from https://github.com/hubverse-org/hubverse-actionsDemonstration PR
This is also an example of a release pull request aligned with the guidelines in https://github.com/orgs/hubverse-org/discussions/29.
Last week, I set this repository to be sent to the R universe upon GitHub release: hubverse-org/hubverse-org.r-universe.dev@82376c5
When #37 was merged into main, it was merged as a development feature and when this PR is merged, I will create a tag and release, which will update the R universe.
Since this is a demonstration, after I release the package, I will revert hubverse-org/hubverse-org.r-universe.dev@82376c5 to go back to our original release-from-main workflow until I have sufficiently updated the documentation and addressed developer concerns.