Skip to content

No new release tag since Aug 2024 #704

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

Open
StephenHodgson opened this issue Apr 28, 2025 · 5 comments
Open

No new release tag since Aug 2024 #704

StephenHodgson opened this issue Apr 28, 2025 · 5 comments

Comments

@StephenHodgson
Copy link

Great package but I'd like to import it from OpenUPM but that requires a new release tag. Thanks!

@StephenHodgson StephenHodgson changed the title No new release tag since Nov 2024 No new release tag since Aug 2024 Apr 28, 2025
@JamesMcGhee
Copy link
Contributor

Add the form Git URL is how we usually import it

That said I do generally recommend you clone the repo locally and add from Disk. This way, you can source control that specific version with your project, and if needed, make changes as opposed to pulling directly off Riley's repo.

But yes it would be nice to have a more reliable versioning, not just in Git but also in the package.json it would let us do more conditional compilation so our tools can account for the evolving SDK

@StephenHodgson
Copy link
Author

All that is required is that a new release commit tag is published to the repo and I can track it easily enough.

@JamesMcGhee
Copy link
Contributor

JamesMcGhee commented May 17, 2025

All that is required is that a new release commit tag is published to the repo and I can track it easily enough.

I wasn't disagreeing with you

yes it would be nice to have a more reliable versioning, not just in Git but also in the package.json it would let us do more conditional compilation so our tools can account for the evolving SDK

@StephenHodgson
Copy link
Author

StephenHodgson commented May 17, 2025

The down thumb was accidental (I as quickly replying from mobile) 😅 It is fixed now.

also in the package.json it would let us do more conditional compilation

💯 agree with this. I actually didn't realize the package was missing this critical information.

Edit, there is a package.json. I'm assuming to be sure to also version the json, yes.

@JamesMcGhee
Copy link
Contributor

The package.json is there ya, but like any version ... its subject to not so reliable update :)

It would help us as tools devs that build on top of @rlabrecque wonderful work if it were a reliable version number in particular if it mapped in some way to the version of Steamworks SDK in use ... sorta related Feedback from me in #662 on that

But ya you really cant trust the Release folder or tags at all at the moment, they aren't updated frequently enough and can often be very out of date. So we generally recomend (to our Discord community) to clone the repo and check the Checkin notes to find the checkins that deal wtih the desired Steamworks SDK version.

Steamworks SDK is not static at all, and lately it seems Valve has been doing quite a bit includign some breaking changes so being aware of what Steamworks SDK version its built on is important.

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

No branches or pull requests

2 participants