iUpdate NEWS for release
Alexander Larsson
5 years ago
0 | Changes in 1.0 | |
1 | ============== | |
2 | ||
3 | Flatpak 1.0 is the first version in a new stable release series. This | |
4 | new 1.x series is the successor to the 0.10.x series, which was first | |
5 | introduced in October 2017. We recommend everyone shipping flatpak to | |
6 | update to 1.0 so it can become a basic dependency that everyone can | |
7 | rely on. | |
8 | ||
9 | The following release notes describe the major changes since | |
10 | 0.10.0. For a complete overview of Flatpak, please see | |
11 | [docs.flatpak.org](http://docs.flatpak.org/en/latest/). | |
12 | ||
13 | ## For users, app developers and distributors | |
14 | ||
15 | Flatpak 1.0 marks a significant improvement in performance and | |
16 | reliability, and includes a big collection of bug fixes. 1.0 also | |
17 | includes a collection of new features, including: | |
18 | ||
19 | * Faster installation and updates. | |
20 | * Applications can now be marked as end-of-life. App centers and | |
21 | desktops can use this information to warn users and prompt them to | |
22 | update, remove the app or just be aware that support may not be | |
23 | available. | |
24 | * Static permissions now use an up-front verification model: users are | |
25 | asked to confirm app permissions at install time, if an update | |
26 | requires additional permissions, the user must also confirm. | |
27 | * A [new portal](https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.Flatpak) | |
28 | allows apps to create sandboxes and restart themselves. This allows | |
29 | applications to restart themselves after they have been updated (to | |
30 | start using the new version), and to increase sandboxing for parts | |
31 | of the application. | |
32 | * `flatpak-spawn` is a new tool for running host commands (if | |
33 | permissions allow) and creating new sandboxes from an app (this | |
34 | uses the above portals APIs). | |
35 | * Apps can now export D-Bus services for all the D-Bus names they are | |
36 | privileged to own (rather than just the application ID). | |
37 | * Flatpak's support for OCI bundles has been updated to the latest | |
38 | specification. Also, AppData can now be distributed through OCI | |
39 | repositories. | |
40 | * Host TLS certificates are now exposed to applications, using | |
41 | p11-kit-server. This removes a point of friction when accessing | |
42 | network services in some environments. | |
43 | * Apps can now request access the host SSH agent to securely access | |
44 | remote servers or Git repositories. | |
45 | * A new application permission can be used to grant access to | |
46 | Bluetooth devices. | |
47 | * A new `fallback-x11` permission grants X11 access, but only if the | |
48 | user is running in a X11 session. For applications that support | |
49 | both Wayland and X11, this can be used to ensure that the app | |
50 | doesn't have unnecessary X11 access while in Wayland, but still | |
51 | works in an X11 session. | |
52 | * Peer-to-peer installation (via USB sticks or local network) is now | |
53 | enabled and supported by default in all builds. | |
54 | ||
55 | The Flatpak command line also introduces new commands and options, including: | |
56 | ||
57 | * `uninstall --unused` automatically removes unused runtimes and | |
58 | extensions (if you've removed all apps that depend on a runtime, or | |
59 | all the apps you had depending on it have upgraded to a newer | |
60 | version). | |
61 | * New `info` options, including `--show-permissions`, | |
62 | `--file-access`, `--show-location`, `--show-runtime`, `--show-sdk`. | |
63 | * `repair` - fixes broken installs by scanning for errors, removing | |
64 | invalid objects and reinstalling anything that's missing. | |
65 | * `permission-*` - allows interaction with the portals permissions | |
66 | store. This is useful for testing and for getting back to a clean | |
67 | state. | |
68 | * `create-usb` - can be used to prepare an repository to be used as a | |
69 | local updates source. | |
70 | ||
71 | Finally, the command line has a collection of other improvements, such as: | |
72 | ||
73 | * If `--system` or `--user` aren't specified, one is automatically | |
74 | picked if it is obvious (or it will ask if the correct option isn't | |
75 | obvious). | |
76 | * The `install`, `update` and `uninstall` commands now ask for | |
77 | confirmation of changes before proceeding, in order to prevent | |
78 | mistakes, and to show the required application permissions. | |
79 | * The `uninstall` command now does not allow you to remove a runtime | |
80 | if some installed application requires it. | |
81 | * `flatpak remove` is now an alias for `flatpak uninstall`. | |
82 | ||
83 | ## For Linux distributors, OS and platform developers | |
84 | ||
85 | * Flatpak no longer requires a filesystem that supports `xattr`. | |
86 | * Portals are now more cleanly separated from Flatpak, thanks to the | |
87 | document portal and permission store having been moved to | |
88 | `xdg-desktop-portal`. Its recommended that the flatpak package has | |
89 | a weak dependency on `xdg-desktop-portal`. | |
90 | * `libflatpak` now has a transaction API for install, update and | |
91 | uninstall operations. This means that it is much easier to use as | |
92 | the basis of app centers and other graphical app management | |
93 | software. | |
94 | * Flatpak now sets several HTTP headers when installing applications, | |
95 | which make it easier for Flatpak repositories to log things like | |
96 | app download statistics and Flatpak versions in use. | |
97 | * It is now recommended that Flatpak packages add a dependency on | |
98 | p11-kit-server, as this allows apps to access host | |
99 | certificates. However, this does not need to be a hard dependency. | |
100 | * Requires bubblewrap 0.2.1 or later, and comes bundled with 0.3.0. | |
101 | * Requires OSTree 2018.7. | |
102 | ||
0 | 103 | Major changes in 0.99.3 |
1 | 104 | ======================= |
2 | 105 |