Skip to content

Correct version number for downstream#18

Closed
Growl1234 wants to merge 1 commit into
hfp:mainfrom
Growl1234:main
Closed

Correct version number for downstream#18
Growl1234 wants to merge 1 commit into
hfp:mainfrom
Growl1234:main

Conversation

@Growl1234

Copy link
Copy Markdown
Collaborator

No description provided.

@Growl1234 Growl1234 requested a review from hfp June 25, 2026 14:51
@hfp

hfp commented Jun 25, 2026

Copy link
Copy Markdown
Owner

If tests go through, I will move the 1.0.0 tag and update the release.

@Growl1234

Growl1234 commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator Author

I saw the changes. If tag is renamed to 1.0.0 this PR won't be need.

@Growl1234 Growl1234 closed this Jun 25, 2026
@hfp

hfp commented Jun 25, 2026

Copy link
Copy Markdown
Owner

I saw the changes. If tag is renamed to 1.0.0 this PR won't be need.

Still, it did not work so far given the new tag.

@hfp

hfp commented Jun 25, 2026

Copy link
Copy Markdown
Owner

( Obviously, I will take the learning to LIBXSTREAM too )

@Growl1234

Copy link
Copy Markdown
Collaborator Author

I saw the changes. If tag is renamed to 1.0.0 this PR won't be need.

Still, it did not work so far given the new tag.

I think those tests need to be re-triggered...

@Growl1234

Copy link
Copy Markdown
Collaborator Author

I found the issue. The tag is named 1.0.0 rather v1.0.0. Let me try to handle it.

@Growl1234

Copy link
Copy Markdown
Collaborator Author

#19

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