question: github org change, redirects work but our scanning/analysis throws flags, preferred approach? #54
Description
Hi,
Our scanning throws up that this package has redirects and the change of org. It's not a massive biggie but it's still noise and annoying.
I'll PR the mod/path import updates - but I think if you feel that's welcome the right course of action is for a breaking change version bump.
This way everyone importing github.com/sst/*/ will have no impact, and new importers @latest will not get a change of package name on import, which needless to say is confusing for us humans and triggers some systems.
Obviously the downside to that is the annoying perception that one string of text carries more weight than another v1.x vs v0.19.x