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
Thinking about this--this gets substituted at build time, the core repo gets built, then it commit+pushes to the dist repo. I believe the way to handle this through the automation in #777 is to ensure we substitute the right version before we scaffold a release/tag in the dist repo. We can detect that we are building a tag in Travis.
To fix it currently, @eonarheim could patch the tag and re-publish over 0.11 or issue a patch release tag (0.11.1).
Excalibur 0.11.0 does not show the correct label in the browser console (0.10.0 does, but this was prior to our automatic version proliferation).
Steps to Reproduce
npm install excalibur@0.11.0
then
Check the "Powered by Excalibur.js" text in the browser console.
Expected Result
"Powered by Excalibur.js (v0.11.0)"
Actual Result
Environment
The text was updated successfully, but these errors were encountered: