Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps-dev): bump @stackexchange/stacks from 2.2.0 to 2.3.0 #293

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

dancormier
Copy link
Contributor

@dancormier dancormier commented Mar 20, 2024

This PR updates Stacks Classic from 2.2.0 to 2.3.0 and makes updates to the markdown toggle to support the new button group styling.

@CGuindon when you have a sec, check out the deploy preview and let me know if it looks ok to you. The button padding needed to be tweaked, so if you'd like the button padding tweaked further let me know.

Once this is approved, I'll cut a new stacks-editor release with this change and update our Core PR for updating Stacks with it, which will resolve the button group issue mentioned there.

image

Copy link

netlify bot commented Mar 20, 2024

Deploy Preview for stacks-editor ready!

Name Link
🔨 Latest commit 2fbca29
🔍 Latest deploy log https://app.netlify.com/sites/stacks-editor/deploys/65fb52e685298b00080ed5f4
😎 Deploy Preview https://deploy-preview-293--stacks-editor.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dancormier dancormier marked this pull request as ready for review March 20, 2024 21:34
@giamir
Copy link
Contributor

giamir commented Mar 21, 2024

@dancormier if you are planning to cut a release for this soon I would recommend to merge this one liner from this PR as well. This is because there is a PR in Core that is using a release candidate version of the editor which might break things in case they merge it.

@dancormier
Copy link
Contributor Author

if you are planning to cut a release for this soon I would recommend to merge this one liner from this PR as well. This is because there is a PR in Core that is using a release candidate version of the editor which might break things in case they merge it.

Holding off on merging the one-liner PR mentioned since it seems like it may need more work to fully address the issue. See https://stackexchange.slack.com/archives/C27RWNQN9/p1711033224917009?thread_ts=1710794302.118679&cid=C27RWNQN9

@dancormier dancormier merged commit 9d5d0e5 into main Mar 21, 2024
5 checks passed
@dancormier dancormier deleted the dcormier/stacks-2-3-0 branch March 21, 2024 20:08
@giamir
Copy link
Contributor

giamir commented Mar 22, 2024

@dancormier I think as part of this upgrade we should have probably bumped the stacks classic peer dependency version to ^2.3.0 in the package.json. I am assuming that the markup changes you made as part of this PR made UI using editor 0.10.4 and stacks classic 2.1.0 look a bit funky. Is that a correct assumption?
If yes, let's push to the main branch the adjustment of the peer dependency to stacks classic ^2.3.0. This way we will have the correct peer dependency version in the next editor release. Thank you. 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants