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

fix: build min from umd #2283

Merged
merged 3 commits into from
Nov 13, 2021
Merged

fix: build min from umd #2283

merged 3 commits into from
Nov 13, 2021

Conversation

UziTech
Copy link
Member

@UziTech UziTech commented Nov 13, 2021

Marked version: 4.0.2

Markdown flavor: Markdown.pl|CommonMark|GitHub Flavored Markdown|n/a

Description

Build marked.min.js from the umd file

Contributor

  • Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
  • no tests required for this PR.
  • If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

@vercel
Copy link

vercel bot commented Nov 13, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/markedjs/markedjs/826NSK7GfSgv7qqhpY7UWVtbo8GT
✅ Preview: https://markedjs-git-uzitech-patch-1-markedjs.vercel.app

@UziTech UziTech merged commit ea26ea9 into master Nov 13, 2021
@UziTech UziTech deleted the UziTech-patch-1 branch November 13, 2021 04:32
github-actions bot pushed a commit that referenced this pull request Nov 13, 2021
## [4.0.3](v4.0.2...v4.0.3) (2021-11-13)

### Bug Fixes

* build min from umd ([#2283](#2283)) ([ea26ea9](ea26ea9))
@github-actions
Copy link

🎉 This PR is included in version 4.0.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

4.0.2 broke current functionality
2 participants