Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@SimonN
Copy link
Collaborator

@SimonN SimonN commented Apr 8, 2025

Before, DMD 2.111.0 produced twice the following deprecation warning: "Deprecation: auto and ref storage classes should be adjacent"

https://dlang.org/changelog/2.111.0.html#dmd.auto-ref-put-adjacent

Now, package optional builds warning-free and deprecation-free with the recently released DMD 2.111.0.

Before, DMD 2.111.0 produced twice the following deprecation warning:
"Deprecation: `auto` and `ref` storage classes should be adjacent"

https://dlang.org/changelog/2.111.0.html#dmd.auto-ref-put-adjacent

Now, package optional builds warning-free and deprecation-free
with the recently released DMD 2.111.0.
Copy link
Owner

@aliak00 aliak00 left a comment

Choose a reason for hiding this comment

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

Oh wow! I'm so out of D and its ecosystem now. This looks perfectly fine - but I have no idea how to release a new version anymore 😆 - let's hope I figure it out :P

@aliak00 aliak00 merged commit e9b5530 into aliak00:main Apr 9, 2025
@SimonN SimonN deleted the autoref branch April 9, 2025 09:07
@SimonN
Copy link
Collaborator Author

SimonN commented Apr 9, 2025

Thanks for the quick merge!

@SimonN
Copy link
Collaborator Author

SimonN commented Apr 9, 2025

no idea how to release a new version anymore

Dub documentation about publishing says:

  1. Tag the newest commit with a semver-looking version.
  2. Push the tag to this public repo.
  3. Wait an hour. The registry knows about this public repo and will find the tag by itself.

@aliak00
Copy link
Owner

aliak00 commented Apr 9, 2025

Ooh that sounded easy enough. Tried that just now 🤞

Btw @SimonN - would you like to take this over if I just gave you access so you can fix whatever you need to and push and merge and all that jazz? :p I do not see myself getting into this anytime soon given my current status/situation!

@SimonN
Copy link
Collaborator Author

SimonN commented Apr 9, 2025

It looks like the dub package registry updater hasn't found the tag yet. Package optional on the registry is still at v1.3.0.

From looking at your past releases, a lightweight tag should be enough. The updater saw the v1.3.0 lightweight tag from 4 years ago, therefore it should see your v1.3.1 lightweight tag, too.

I asked in the D IRC channel (#d on Libera). Insights:

  • The updater can be slow. You, as package maintainer, can force the registry to update. Log into the dub registry, then go to the maintainer page of optional on dub ("manage package"), and have the registry scan sooner.
  • It's not necessary to "create a release from tag" on Github. Pushing a tag should have been sufficient.
  • It's not clear whether lightweight tags or annotated tags are required, but I still believe that lightweight tags are enough because it worked 4 years ago with the lightweight tag.

Thanks for your trust and the offer of successorship! That would be my first dub package to maintain. I'll sleep over it a few days, and come back to you with an answer.

@aliak00
Copy link
Owner

aliak00 commented Apr 10, 2025

Ah of course, log in :D Got in and clicked the button, seems like it updated?

Screenshot 2025-04-10 at 10 15 50

And yeah sure! just let me know whenever!

@SimonN
Copy link
Collaborator Author

SimonN commented Apr 11, 2025

Yes, that was it; the package registry has the 1.3.1 now. Thanks! (The dub site happens to be down today, but I saw the 1.3.1 correctly there earlier.)

I've decided: Yes, I'm happy to become maintainer of the optional package. I have an active client project (Lix) that uses optional, therefore I see the occasional breakage in optional early. I've submitted PRs to optional like this one, and yesterday, I've dug into the details of the dub packaging/versioning process.

I don't have an account on the dub package registry, but I'll be busy this weekend. I'll open an account there in 0-3 weeks.

I haven't published API documentation web pages yet. I'm interested in better type/functor/monad support in D itself, but I won't invest much time to push such an issue with D directly.

@aliak00
Copy link
Owner

aliak00 commented Apr 12, 2025

Awesome! I've added you to this repo now, so I think you can do whatever you want. If there're any issues then feel free to just ping back here. Let me know if I have to do anything in DUB to "permit" the transfer there or anything so you can just release whenever you want to too!

@aliak00
Copy link
Owner

aliak00 commented Apr 12, 2025

I guess if it's just about pushing a tag, the opening account account is not strictly necessary, but it would be convenient to click the buttons I had to click yesterday or whatever to force pickup a tag release :D

@SimonN
Copy link
Collaborator Author

SimonN commented Apr 13, 2025

All right, thanks!

I'll let you know when I make an account for the dub package registry.

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