Upgrade unexpected to version 11.0.0 #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ unexpected (11.0.0-4 → ^11.0.0) · Repo · Changelog
Release Notes
11.0.0 (from changelog)
Commits
See the full diff on Github. The new version differs by 44 commits:
11.0.0Build unexpected.jsRevert "REVERT once v11 is out of beta: Specify tag:beta in package.json"Revert "REVERT ME when merging v11 to master: Don't deploy the documentation site when doing releases"Merge pull request #509 from unexpectedjs/v11Docs: Use https urls on the plugin page, fix a dead linkDocs: List unexpected-preact on the plugins pageDocs: Mention that node.js < 6 is unsupported per Unexpected 11Merge branch 'docs/migrationGuide' into v11Merge branch 'master' into v11Tweak a section heading.Mention the two additional deprecations on the release and migration pagesFix typosMerge pull request #567 from unexpectedjs/chore/unsupportThisInAssertionsMerge pull request #566 from unexpectedjs/chore/removeExpectAsyncRemove long-deprecated support for this.subject etc. in assertion handlersRemove expect.asyncMerge pull request #564 from unexpectedjs/depfu/update/npm/unexpected-documentation-site-generator-5.1.0Update unexpected-documentation-site-generator to version 5.1.0Merge pull request #563 from unexpectedjs/depfu/update/npm/rollup-1.0.1Update rollup to version 1.0.1Merge branch 'master' into v11Merge pull request #546 from unexpectedjs/cleanup/fixTestScriptWithLocalBrowserMerge pull request #556 from unexpectedjs/feature/simplifyToBeRejectedWithMerge pull request #559 from unexpectedjs/fix/preferredWidthPropagationMerge pull request #561 from unexpectedjs/ssimonsen/relative-doc-urlsMerge pull request #562 from unexpectedjs/fix/httpRedirectsAvoid http redirects in assets linked from the frontpageMade all internal doc URL's relative and with a trailing slashAdd a separate releases page with an entry for 11.0.0Stop generating a menu entry for the migration pageShow the expect.it() function argument syntax.Add a function by value example.Convert all assertion references to links.Fix rendering the hyphen.Don't let changes to expect.output.preferredWidth propagate into existing clonesREVERT ME when merging v11 to master: Don't deploy the documentation site when doing releasesAvoid using arrow functions in tests where they're being inspectedEmpty commit to see if netlify picks up11.0.0-4Build unexpected.jsFix tests merged from master so they work with the transpiled browser testsMerge branch 'master' into v11Updated the changelogDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands