There's one other external package right now: @sunbeams/eslint-config but this will change in the future. Keeping them version pinned at the moment is fine - the expectation is that the eslint-config isn't generally being used on it's own; just use sunbeams. But at some point this breaks down and I'd like a better solution before the full release.
Considerations:
I like GitHub releases a lot, and would prefer to keep that without it getting confusing. I don't know that this is possible though. There may be some way to have a sunbeams version of the repo that is separate from each individual package - which I don't hate. Either way, something to work out.
There's one other external package right now: @sunbeams/eslint-config but this will change in the future. Keeping them version pinned at the moment is fine - the expectation is that the eslint-config isn't generally being used on it's own; just use sunbeams. But at some point this breaks down and I'd like a better solution before the full release.
Considerations: I like GitHub releases a lot, and would prefer to keep that without it getting confusing. I don't know that this is possible though. There may be some way to have a
sunbeamsversion of the repo that is separate from each individual package - which I don't hate. Either way, something to work out.