Skip to content

Conversation

sjvans
Copy link
Contributor

@sjvans sjvans commented Aug 7, 2025

@David-Kunz @chgeo anything to do from your side before we can create a 0.0.1 release on github (no need to promote to npm)?

@sjvans sjvans requested review from David-Kunz and chgeo August 7, 2025 15:26
@sjvans sjvans marked this pull request as ready for review August 7, 2025 15:27
Copy link
Member

@chgeo chgeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hold on.
@timlizzy just contacted me that management tends to not make it open source. He will give us an update soon.

@chgeo chgeo closed this Aug 8, 2025
@chgeo chgeo deleted the prep-v0.0.1 branch August 8, 2025 10:20
@sjvans sjvans restored the prep-v0.0.1 branch August 13, 2025 14:25
@sjvans sjvans reopened this Aug 13, 2025
@sjvans sjvans requested a review from chgeo August 13, 2025 14:37
@sjvans
Copy link
Contributor Author

sjvans commented Aug 13, 2025

@chgeo @David-Kunz next try ;) again, only a github release (not yet to npm)

@chgeo
Copy link
Member

chgeo commented Aug 14, 2025

@sjvans I have added a release workflow + will configure the NPM token.
You can decide to release at any time. The workflow must be triggered manually.

@chgeo chgeo merged commit 17fe5f5 into main Aug 14, 2025
4 checks passed
@chgeo chgeo deleted the prep-v0.0.1 branch August 14, 2025 09:11
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