Legacy Environment Variables Detected

[begunfx]

Seeing the following when I bump my version to 1.5.0-rc.1

There is no information on what the replacement env variables should be or a place to go to view them. I would recommend changing the "Don't Show Again" button to a small checkbox underneath the message and use that button for "Details" that can take the user to documentation of the warning so we can take action on it.

[s-b-e-n-s-o-n]

Good feedback — you're right, the banner should tell you what to do, not just that something's wrong.

I've updated the deprecation banners to:

1. Show the migration path inline — the banner now says "Rename WUD_* vars to DD_* and DD_TRIGGER_* to DD_ACTION_* or DD_NOTIFICATION_*" instead of just listing the old keys
2. Link directly to the migration guide — each banner now has a "View migration guide" link that takes you to the deprecation schedule page, which has per-item migration instructions and CLI commands

The legacy hash banner also got the same treatment (links to the specific section on migrating to argon2id).

These changes will land in the next RC. The deprecation schedule page at getdrydock.com/docs/deprecations will be the single reference for all deprecated features, removal versions, and migration steps.

[s-b-e-n-s-o-n]

Landed — the deprecation banners now show the rename inline (WUD_* → DD_*, DD_TRIGGER_* → DD_ACTION_*/DD_NOTIFICATION_*) and each one has a View migration guide link to the relevant anchor on getdrydock.com/docs/deprecations. The legacy hash banner got the same treatment with the argon2id re-hash one-liner. Will be live in v1.5.0-rc.10 when it cuts shortly — give it a spin.