Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare 0.2.0.1 release. #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Prepare 0.2.0.1 release. #1

wants to merge 1 commit into from

Conversation

brianjosephmckeon
Copy link
Member

Removed other subprojects.
Reformatted.
Use new .github workflows.
Updated changelog.

Removed other subprojects.
Reformatted.
Use new .github workflows.
Updated changelog.
@brianjosephmckeon
Copy link
Member Author

brianjosephmckeon commented Mar 7, 2024

@andrewthad Got some weird stuff going on with some of the projects.

If you look at the most recent workflow run for this PR, you'll see that certain modules aren't being exposed by siphon and colonnade.

I already moved siphon into its own repo. I was able to build the code, but VSC reported some errors that I ignored because I thought it was just VSC being weird. But now I'm wondering if it was actually trying to tell me something useful.

I also have an open PR for the colonnade repo. Feel free to make any changes you need to in that PR.

You may also notice warnings in these projects related to unused functions, etc. I left them in there because they weren't hurting anything. But since you'll be looking at these projects anyway, it might be good to remove anything that isn't being used.

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.

1 participant