# Release 1.0.0 **URL:** \ **Category:** Announce\ **Created:** [October 13, 2017, 12:43pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998 "2017-10-13T12:43:59Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![marijn](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/marijn/32/15_2.png) [@marijn](https://discuss.prosemirror.net/u/marijn)\ **Post date:** [October 13, 2017, 12:43pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/1 "2017-10-13T12:43:59Z")
Well, it’s finally happening, on Friday the 13th no less: ProseMirror 1.0 [has been released](http://marijnhaverbeke.nl/blog/prosemirror-1.html). In the future, the packages will no longer be versioned and released in lockstep (I’m looking into setting up some largely-automated release process so that I can quickly fire off minor releases). New features will go through [the RFC process](https://github.com/prosemirror/rfcs/), and backwards-compatibility will be prioritized. I couldn’t help working on a few more things right before the release. Nothing scary or breaking, but if you run into a regression, let me know and I’ll try to quickly resolve it with a patch release. # Release notes ## [prosemirror-model](http://prosemirror.net/docs/ref/#model) 1.0.0 (2017-10-13) ### New features [`ParseRule.context`](http://prosemirror.net/docs/ref/#model.ParseRule.context) may now include multiple, pipe-separated context expressions. ## [prosemirror-transform](http://prosemirror.net/docs/ref/#transform) 1.0.0 (2017-10-13) ### Bug fixes When [`setBlockType`](http://prosemirror.net/docs/ref/#transform.Transform.setBlockType) comes across a textblock that can’t be changed due to schema constraints, it skips it instead of failing. [`canSplit`](http://prosemirror.net/docs/ref/#transform.canSplit) now returns false when the requested split goes through isolating nodes. ## [prosemirror-view](http://prosemirror.net/docs/ref/#view) 1.0.0 (2017-10-13) ### Bug fixes Dragging nodes with a node view that handles its own mouse events should work better now. List item DOM nodes are no longer assigned `pointer-events: none` in the default style. Ctrl-clicking list markers now properly selects the list item again. Arrow-down through an empty textblock no longer causes the browser to forget the cursor’s horizontal position. Copy-dragging on OS X is now done by holding option, rather than control, following the convention on that system. Fixes a crash related to decoration management. Fixes a problem where using cut on IE11 wouldn’t actually remove the selected text. Copy/paste on Edge 15 and up now uses the clipboard API, fixing a problem that made them fail entirely. ### New features The [`dragging`](http://prosemirror.net/docs/ref/#view.EditorView.dragging) property of a view, which contains information about editor content being dragged, is now part of the public interface. ## [prosemirror-commands](http://prosemirror.net/docs/ref/#commands) 1.0.0 (2017-10-13) ### New features The [`setBlockType` command](http://prosemirror.net/docs/ref/#commands.setBlockType) can now be used to change the types of multiple selected textblocks (rather than only one). The platform-dependent versions of the [base keymap](http://prosemirror.net/docs/ref/#commands.baseKeymap) are now exported separately as [`pcBaseKeymap`](http://prosemirror.net/docs/ref/#commands.pcBaseKeymap) and [`macBaseKeymap`](http://prosemirror.net/docs/ref/#commands.macBaseKeymap). ## [prosemirror-gapcursor](http://prosemirror.net/docs/ref/#gapcursor) 1.0.0 (2017-10-13) ### New features Valid gap cursor positions are not determined in a way that allows them inside nested nodes. By default, any position where a textblock can be inserted is valid gap cursor position. Nodes can override whether they allow gap cursors with the `allowGapCursor` property in their spec. ---
**Author:** ![johanneswilm](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/johanneswilm/32/19_2.png) [@johanneswilm](https://discuss.prosemirror.net/u/johanneswilm)\ **Post date:** [October 13, 2017, 2:42pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/2 "2017-10-13T14:42:52Z")
Congratulations! One little issue: If you place the caret in the middle of the first sentence in the demo on [https://prosemirror.net](https://prosemirror.net) and then hit enter, it does not split the paragraph. Also paragraph merging does not seem to work any more. Tested on Chrome 61 and Firefox 56. Same happens when I try it out with our code. ---
**Author:** ![marijn](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/marijn/32/15_2.png) [@marijn](https://discuss.prosemirror.net/u/marijn)\ **Post date:** [October 13, 2017, 3:07pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/3 "2017-10-13T15:07:34Z")
Argh, that’s bad—I screwed up one of those last-second changes. Released prosemirror-commands 1.0.1 with a fix. ---
**Author:** ![johanneswilm](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/johanneswilm/32/19_2.png) [@johanneswilm](https://discuss.prosemirror.net/u/johanneswilm)\ **Post date:** [October 13, 2017, 3:26pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/4 "2017-10-13T15:26:19Z")
working now. ---
**Author:** ![wes-r](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/wes-r/32/77_2.png) [@wes-r](https://discuss.prosemirror.net/u/wes-r)\ **Post date:** [October 13, 2017, 10:22pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/5 "2017-10-13T22:22:27Z")
Congratulations! Been great watching this project progress, I can only imagine how rewarding it must be for you to see it hit 1.0! ---
**Author:** ![kzap](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/kzap/32/419_2.png) [@kzap](https://discuss.prosemirror.net/u/kzap)\ **Post date:** [October 15, 2017, 2:35pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/6 "2017-10-15T14:35:32Z")
Congrats! It’s been a long road. Glad to see ProseMirror hit a milestone and advance this part of the web… maybe they will finally fix contentEditable 😃 ---
**Author:** ![abhinavzspace](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/abhinavzspace/32/611_2.png) [@abhinavzspace](https://discuss.prosemirror.net/u/abhinavzspace)\ **Post date:** [October 16, 2017, 4:07am UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/7 "2017-10-16T04:07:10Z")
Congratulations! @marijn ---
**Author:** ![kiejo](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/kiejo/32/64_2.png) [@kiejo](https://discuss.prosemirror.net/u/kiejo)\ **Post date:** [October 16, 2017, 8:17am UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/8 "2017-10-16T08:17:22Z")
Awesome work 🙂 Congrats! ---
**Author:** ![elgow](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/elgow/32/421_2.png) [@elgow](https://discuss.prosemirror.net/u/elgow)\ **Post date:** [October 16, 2017, 10:08pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/9 "2017-10-16T22:08:36Z")
Congratulations on the 1.0 release. I note that you marked the 1.0 versions with a commit. Will there be any tags, branches, etc. to make getting the proper versions from github easier? ---
**Author:** ![marijn](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/marijn/32/15_2.png) [@marijn](https://discuss.prosemirror.net/u/marijn)\ **Post date:** [October 17, 2017, 6:21am UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/10 "2017-10-17T06:21:40Z")
> [@elgow](#): > > Will there be any tags, branches, etc. to make getting the proper versions from github easier? Yes, each release is tagged in the repositories. ---
**Author:** ![johnking](https://discuss.prosemirror.net/letter_avatar_proxy/v4/letter/j/b5e925/32.png) [@johnking](https://discuss.prosemirror.net/u/johnking)\ **Post date:** [October 18, 2017, 11:34pm UTC](https://discuss.prosemirror.net/t/release-1-0-0/998/11 "2017-10-18T23:34:42Z")
Congratulations on the 1.0 release.