Update changelog

This commit is contained in:
Jonatan Kłosko 2025-02-05 01:38:38 +07:00
parent cb11217c23
commit 768d01f81f
2 changed files with 36 additions and 1 deletions

View file

@ -4,6 +4,41 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
## [Unreleased](https://github.com/livebook-dev/livebook/tree/main) ## [Unreleased](https://github.com/livebook-dev/livebook/tree/main)
### Added
* Support for defining modules in the Erlang cell ([#2806](https://github.com/livebook-dev/livebook/pull/2806))
* Option to specifying erl flags for Standalone runtime node ([#2843](https://github.com/livebook-dev/livebook/pull/2843))
* Support for specifying max height on grid output ([#2846](https://github.com/livebook-dev/livebook/pull/2846))
* Introduced authentication via Livebook Teams for Livebook app servers, including third-party SSO integrations ([#2837](https://github.com/livebook-dev/livebook/pull/2837), [#2919](https://github.com/livebook-dev/livebook/pull/2919))
* HTTP proxy configuration via env variables (`HTTP_PROXY`, `HTTPS_PROXY`) ([#2850](https://github.com/livebook-dev/livebook/pull/2850))
* Deployment group environment variables included in generated Livebook app server instructions ([#2858](https://github.com/livebook-dev/livebook/pull/2858))
* Added Clickhouse to the database connection cell options ([#2840](https://github.com/livebook-dev/livebook/pull/2840))
* Logs whenever code is evaluated evaluation (level info) ([#2880](https://github.com/livebook-dev/livebook/pull/2880))
* Added `LIVEBOOK_LOG_LEVEL` and `LIVEBOOK_LOG_METADATA` for customizing logged information ([#2880](https://github.com/livebook-dev/livebook/pull/2880))
* Shell code block highlighting in Markdown cells
* Added a custom view option that hides code ([#2889](https://github.com/livebook-dev/livebook/pull/2889))
* Information accessed via `Kino.Workspace.info()` to include payload returned from identity provider ([#2890](https://github.com/livebook-dev/livebook/pull/2890))
### Changed
* (Desktop) The server to start on a fixed port by default (`32123`) and fall back to random if taken ([#2867](https://github.com/livebook-dev/livebook/pull/2867))
* Bumped versions to Elixir 1.18.2 and Erlang 27.2.1 in the Docker image and the desktop app
* Bumped the required Elixir version to 1.18
* In case you set `RELEASE_DISTRIBUTION`, it has been ignored since v0.13, but now it must not be set
### Removed
* Removed `LIVEBOOK_APPS_PATH_HUB_ID` in favour of `LIVEBOOK_TEAMS_AUTH` ([#2829](https://github.com/livebook-dev/livebook/pull/2829))
### Fixed
* Proper namespace to be selected when reopening K8s runtime settings
* Importing notebook via livebook.dev/run to download attachments
* Kino forms to not emit change event on the first render ([#2852](https://github.com/livebook-dev/livebook/pull/2852))
* (Desktop) "Copy URL" not pasting properly into Terminal
* (Desktop) Subsequent installations on Windows leading to conflicting Hex archives ([#2859](https://github.com/livebook-dev/livebook/pull/2859))
* Erlang snippets in Markdown cells being exported as Erlang code cells
## v0.14 ## v0.14
The CHANGELOG for v0.14 releases can be found in the [v0.14](https://github.com/livebook-dev/livebook/tree/v0.14/CHANGELOG.md) branch. The CHANGELOG for v0.14 releases can be found in the [v0.14](https://github.com/livebook-dev/livebook/tree/v0.14/CHANGELOG.md) branch.

View file

@ -95,7 +95,7 @@ with [Nerves](https://www.nerves-project.org/).
### Direct installation with Elixir ### Direct installation with Elixir
You can run Livebook on your own machine using just Elixir. You will need You can run Livebook on your own machine using just Elixir. You will need
[Elixir v1.16](https://elixir-lang.org/install.html) or later. [Elixir v1.18](https://elixir-lang.org/install.html) or later.
Livebook also requires the following Erlang applications: `inets`, Livebook also requires the following Erlang applications: `inets`,
`os_mon`, `runtime_tools`, `ssl` and `xmerl`. Those applications come `os_mon`, `runtime_tools`, `ssl` and `xmerl`. Those applications come
with most Erlang distributions but certain package managers may split with most Erlang distributions but certain package managers may split