Skip to content

Add rivertype module to release instructions#244

Merged
brandur merged 1 commit intomasterfrom
brandur-rivertype
Mar 1, 2024
Merged

Add rivertype module to release instructions#244
brandur merged 1 commit intomasterfrom
brandur-rivertype

Conversation

@brandur
Copy link
Contributor

@brandur brandur commented Mar 1, 2024

As of #212, rivertype became a separate Go module from the mainline
river. Here, add it to the release instructions so that it gets
properly tagged along with other all other modules.

Also add it to the update-submodule-versions program. This isn't
strictly necessary because rivertype doesn't have any submodule
versions to update, but it feels like it should be there for
completeness just in case, and also because it makes the list in the
program a complete list of all Go modules in the project.

As of #212, `rivertype` became a separate Go module from the mainline
`river`. Here, add it to the release instructions so that it gets
properly tagged along with other all other modules.

Also add it to the `update-submodule-versions` program. This isn't
strictly necessary because `rivertype` doesn't have any submodule
versions to update, but it feels like it should be there for
completeness just in case, and also because it makes the list in the
program a complete list of all Go modules in the project.
@brandur
Copy link
Contributor Author

brandur commented Mar 1, 2024

ty!

@brandur brandur merged commit dcc2a19 into master Mar 1, 2024
@brandur brandur deleted the brandur-rivertype branch March 1, 2024 04:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants