You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@hundt-corbalt, it's strange that that commit is showing up under the @cmsgov/design-system@7.0.7 tag, and I still haven't figured out why. We didn't release it until v8.0.0. I think something went wrong with our release tagging, because our intention wasn't to release it until 8.0.0.
It's also curious how the commit is in the history of that tagged release commit, and yet our publishing infrastructure that checks out a specific tag didn't publish code with that commit to npm. I can see in the 7.0.7 publishing logs that @cmsgov/design-system@7.0.7 was checked out. If I check out that tag locally, I see the tab commit in the commit log. If I check out the commit that our publish job was on after it checked out that tag, the tab commit is not in the commit log. So at this point I'm not sure if it's a bug in our publish job, a bug in our release script that tags the commit, or GitHub modifying tags.
I updated to 7.0.7 to get this commit. If you look at
https://github.com/CMSgov/design-system/blob/%40cmsgov/design-system%407.0.7/packages/design-system/src/components/Tabs/TabPanel.tsx
You can see the commit applied:
But the actual code uploaded to NPM does not seem to include this commit:
https://www.npmjs.com/package/@cmsgov/design-system/v/7.0.7?activeTab=code
The text was updated successfully, but these errors were encountered: