Skip to content

Conversation

@chuckadams
Copy link

@chuckadams chuckadams commented Jan 2, 2026

I've tested the command in isolation, and it's known to work, but the only real way to test the action is to just tag a test release and let it do its thing. We can use a tag like 0.0.1-exp which has no danger of causing an update, and remove it after.

This address part of #411 but does not close it.

Signed-off-by: Chuck Adams <chaz@chaz.works>
@chuckadams chuckadams requested review from Ipstenu and ramseyp January 2, 2026 22:43
@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2026

@toderash toderash moved this to Icebox in FAIR Connect Jan 2, 2026
@Ipstenu Ipstenu added this to the 1.3 milestone Jan 2, 2026
@Ipstenu Ipstenu changed the base branch from main to release_1.3.0 January 2, 2026 23:29
Signed-off-by: Chuck Adams <chaz@chaz.works>
@chuckadams chuckadams merged commit 7bf73c5 into release_1.3.0 Jan 3, 2026
2 checks passed
@chuckadams chuckadams deleted the gh_411_upload_release_assets branch January 3, 2026 00:27
@github-project-automation github-project-automation bot moved this from Icebox to Done in FAIR Connect Jan 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants