robotcode 2.8.0.dev631__tar.gz → 2.8.0.dev670__tar.gz

{robotcode-2.8.0.dev631 → robotcode-2.8.0.dev670}/CHANGELOG.md

@@ -61,6 +61,16 @@ All notable changes to this project will be documented in this file. See [conven
 
   The documentation site is rebuilt on Astro and Starlight and reorganized into Getting Started, Guides and Reference by what the reader comes to do. A new home page shows RobotCode's features and an AI agent at work in short demos, and the news get tags and an RSS feed. All pages have new addresses; the old ones lead to the not-found page instead of redirecting. The What's New notification of the VS Code extension opens /news/latest/, which always leads to the newest release notes.
 
+- **intellij:** Use the interpreter of the Robot Framework module ([1c77903](https://github.com/robotcodedev/robotcode/commit/1c77903e1757b875d142e3c34baf0827e95d42f8))
+
+  In a project with several modules, RobotCode now takes the interpreter
+  and the roots of the module that holds the Robot Framework project, not
+  the first module with an interpreter, and asks when several modules
+  qualify; the General page can change the module. Run configurations now
+  show in their editor when their interpreter lacks Robot Framework, a
+  target path is missing or a selected test is gone, and a run checks the
+  interpreter of its own configuration.
+
 - **intellij:** Show each test failure with the calls that led to it ([f577367](https://github.com/robotcodedev/robotcode/commit/f577367253a4b501d84de1659e7419b0755628e9))
 
   A failed test's details in PyCharm now list each failure with its calls as Python lists them, from the call in the test inward, as `File "<file>", line <n>, in <keyword>` with links to the lines. Several failures follow an empty line and each begins with its message, failures the test caught are marked "Caught:", and a keyword such as Wait Until Keyword Succeeds that ends with an error of its own is one failure. A double-click on a failed test now opens the call in the test that led to its first failure, and VS Code's exception widget lists the calls in the same order, from the test down to the failed keyword.
@@ -358,6 +368,7 @@ All notable changes to this project will be documented in this file. See [conven
   `robotcode discover all`, `tests` and `tasks` and `robotcode results show`
   now take `--show-tags / --no-show-tags` instead of `--tags / --no-tags`.
 
+- **vscode:** Copy the versions in use for a report ([1e0d8f8](https://github.com/robotcodedev/robotcode/commit/1e0d8f8b32589035e61f652c428cdcea9e40268e))
 - **vscode:** Open a new Documentation Viewer from a viewer's toolbar ([e4c6fe7](https://github.com/robotcodedev/robotcode/commit/e4c6fe78d11d654676ee0857ad8d77ec0ed84569))
 
   A button at the end of a Documentation Viewer's toolbar opens a new viewer on
@@ -459,6 +470,13 @@ All notable changes to this project will be documented in this file. See [conven
 
   The robotcode command that VS Code terminals fall back to required /bin/bash, which Alpine-based containers, NixOS and FreeBSD don't have, and a space in the extension path, for example from a Windows user name like `John Doe`, split the path into two arguments in sh and cmd.
 
+- **config:** Apply none of the profiles a disabled profile inherits from ([edaa183](https://github.com/robotcodedev/robotcode/commit/edaa183792ecbb1f9de72d6f68731e8fafc61545))
+
+  Selecting a disabled profile still applied the profiles two or more levels up
+  its chain: with ci disabled, inheriting from staging and staging from base,
+  `-p ci` applied base. An inherited profile now applies only when a profile that
+  inherits it applies, and an error in an `enabled` condition is reported once.
+
 - **config:** Apply extend- settings next to the setting they extend ([45eaa5b](https://github.com/robotcodedev/robotcode/commit/45eaa5be64de81459a585c5150681ef994e12622))
 
   A profile or file with both `variables` and `extend-variables` ignored the extend- setting, and an extend- setting in `[extend-profiles.<name>]`, for example in `.robot.toml`, did not add to the setting of the profile it extends. Now the setting applies first and its extend- setting adds to it.
@@ -516,6 +534,13 @@ All notable changes to this project will be documented in this file. See [conven
   macOS ~/Library/Application Support, Windows %LOCALAPPDATA%) so the file
   is placed where RobotCode actually looks for it.
 
+- **intellij:** Leave PyCharm's profilers out of the run marker menu ([0fda1cd](https://github.com/robotcodedev/robotcode/commit/0fda1cd9b538efe1a543a8d3ebb2e61c2b6b8d06))
+
+  The menu of a run marker no longer offers PyCharm Professional's Profile and
+  Concurrency Diagram, which Robot Framework runs don't support. Concurrency
+  Diagram, which More Run/Debug and the run widget still offer, now ends with a
+  message as Profile does, instead of running the test under PyCharm's debugger.
+
 - **intellij:** Remove the gap above tables in the documentation ([7eb4cd3](https://github.com/robotcodedev/robotcode/commit/7eb4cd3f666189ea763fdd60ab98b46a5346ff66))
 
   Quick Documentation, the hover and the Ctrl+hover hint left a large gap between
@@ -651,6 +676,13 @@ All notable changes to this project will be documented in this file. See [conven
   Use the plugin's own RobotCodeBundle with a new command.typing.name key instead. The
   displayed command name ("Typing") is unchanged.
 
+- **language-server:** Offer the documentation actions in inline IF and Run Keyword ([b99fd04](https://github.com/robotcodedev/robotcode/commit/b99fd0409c549d9c2f0ed1f6a83536f63bdd255d))
+
+  With the experimental semantic model, a keyword in the body of an inline
+  IF or in the arguments of Run Keyword and its variants, nested ones too,
+  now has the documentation actions and the link to the Documentation
+  Viewer in the heading of its hover, as without the semantic model.
+
 - **language-server:** List the declaration after the usages in Find References ([a486486](https://github.com/robotcodedev/robotcode/commit/a4864866eee781cb9eb33d54b15878f04e58fd4d))
 
   In PyCharm, LSP Reference(s) did nothing on a library keyword such as `Log`
@@ -777,6 +809,14 @@ All notable changes to this project will be documented in this file. See [conven
   `python-path`, still apply. Run `robotcode --verbose repl` to see which
   options were ignored.
 
+- **robot:** Keep the keyword documentation of a cached semantic model ([27535f5](https://github.com/robotcodedev/robotcode/commit/27535f5385b754ba49aed4d4220854b6cc214414))
+
+  With the experimental semantic model, a file that RobotCode restored from
+  its analysis cache after a restart and that was then opened without changes
+  had no documentation actions, no link in the hover's heading and no
+  documentation links in the signature help for BuiltIn keywords until it was
+  edited. The cached analysis now refers to the keywords of the restored file.
+
 - **robot:** Show no library scope for variable files ([36059ad](https://github.com/robotcodedev/robotcode/commit/36059adbd475eb0390dbeb271d922dd2f1533209))
 
   The hover of a variable file import no longer lists "Library Scope:
@@ -940,6 +980,26 @@ All notable changes to this project will be documented in this file. See [conven
 
   Environment variables no longer swallow the rest of their row, and comments right after a keyword or marker, RETURN, the FOR separators, item access such as ${LIST}[0], AS in EXCEPT and Library, and default values in [Arguments] are highlighted correctly in VS Code, IntelliJ, Markdown views and on the documentation site. REPL scripts and notebook cells now use the same grammar, so multiple assignments, nested variables, BREAK, CONTINUE and GROUP are highlighted there too.
 
+- **vscode:** Fill the Keywords view once the language server has started ([599ad73](https://github.com/robotcodedev/robotcode/commit/599ad73808c54bc7ddf77703acd7d831316004fc))
+
+  When VS Code restores an open Robot Framework file at startup, the Keywords
+  view shows its keywords as soon as the language server runs, without closing
+  and reopening the file. Canceled requests of the view no longer show up as
+  errors in RobotCode's output (#644).
+
+- **vscode:** Show only the run's command line in a reused terminal's sticky scroll ([f3966fe](https://github.com/robotcodedev/robotcode/commit/f3966fea854ee103dd3004f79ad5389501d08301))
+
+  When a run terminal is reused, VS Code's sticky scroll shows only the command
+  line of the current run. Copy Output of a run ends with the line about the
+  terminal's reuse.
+
+- **vscode:** Keep the terminal in front at the first run of a window ([f15c1a5](https://github.com/robotcodedev/robotcode/commit/f15c1a53170271fef7745bf4fc7a7f1ac135e173))
+
+  When a run writes its output to a terminal, VS Code no longer switches the
+  panel to the Debug Console at the first run of a window. A value of
+  debug.internalConsoleOptions in the settings or internalConsoleOptions in a
+  launch configuration still decides when the Debug Console opens.
+
 - **vscode:** Report environment problems at startup only if they remain ([b0cbfaa](https://github.com/robotcodedev/robotcode/commit/b0cbfaad340bc8cfed309df77a3515627f187eae))
 
   While VS Code starts or a folder is added, the Python extension may need
@@ -1051,6 +1111,10 @@ All notable changes to this project will be documented in this file. See [conven
 
   The profile examples replaced `variables` instead of extending them and set a number where a string is required, the user configuration is per user and created when it is missing, profiles with the same precedence keep the order they are selected in, and the `extend-*` keys of the analyze settings only take effect in an `extend-<section>` table such as `[tool.robotcode-analyze.extend-modifiers]`.
 
+- **contributing:** Describe the tests of the VS Code extension and the PyCharm plugin ([44d2551](https://github.com/robotcodedev/robotcode/commit/44d25517a6809af730d483d8fcc2e95f66085e60))
+
+  The contribution guide and the pull request template now ask for the tests of every changed part, explain how to run, try and verify the PyCharm plugin, list what the CI runs and ask for tests that pass on Linux, Windows and macOS. The commit types and scopes match the ones in use.
+
 - **contributing:** Describe how to regenerate the CLI reference ([5ff48c8](https://github.com/robotcodedev/robotcode/commit/5ff48c8ad8c269b553c175ed23d4d04b0bbbed41))
 - **debugger:** Fix the links to exception breakpoints ([5a12cce](https://github.com/robotcodedev/robotcode/commit/5a12ccef5923da11b109fe3510d07e14e3af5c26))
 
@@ -1063,6 +1127,148 @@ All notable changes to this project will be documented in this file. See [conven
   and the first steps, and links to the PyCharm guide on robotcode.io. On
   GitHub, the JetBrains logo shows again.
 
+- **openspec:** Archive the intellij-run-marker-without-profilers change ([cc5de92](https://github.com/robotcodedev/robotcode/commit/cc5de92bcc661c766d47cfaf53daaf87bb36773a))
+
+  Moves the change to the archive, with its tasks checked off and the results of
+  the harness check, and adds its requirement on the run marker's menu and the
+  message of Concurrency Diagram to the main spec intellij-run-configurations.
+
+- **openspec:** Plan a run marker menu without PyCharm's profilers ([d0cfc19](https://github.com/robotcodedev/robotcode/commit/d0cfc197cf15260fe126cdf0d4f5e8ab67dc2b59))
+
+  The run marker of a Robot Framework test is to offer only Run, Debug, the runs
+  with a profile and Modify Run Configuration, without PyCharm's Profile and
+  Concurrency Diagram, and Concurrency Diagram is to end with a message wherever
+  else PyCharm offers it, as Profile does.
+
+- **openspec:** Replace the completion model branch with a parity test ([1fb272b](https://github.com/robotcodedev/robotcode/commit/1fb272bfc7341d439484bccee607c330e7f0c904))
+
+  Completion keeps taking its context from the current text: it works with
+  the namespace of the last finished analysis, whose semantic model still
+  describes the text before the latest keystrokes. The change now proves
+  that completion answers the same on both analysis paths, over the test
+  data, a document with incomplete input and the documents of the
+  completion tests, and fixes what that finds in the SemanticAnalyzer.
+  The TokenKind audit stays; ModelHelper stays in completion until the
+  cleanup.
+
+- **openspec:** Archive the semantic-model-cache-references change ([c5ee95c](https://github.com/robotcodedev/robotcode/commit/c5ee95c6fcdc645fa39c0c648d434b2a3b6e16b0))
+
+  Moves the change to the archive and adds the requirement for a restored
+  semantic model to namespace-cache.
+
+- **openspec:** Complete the semantic-model-cache-references change ([2646e5c](https://github.com/robotcodedev/robotcode/commit/2646e5cbe7ed8baa26a006e07a3d1883c3d77f45))
+
+  All tasks are checked off. The implementation added the inits of variables
+  files to the restore, showed that the fallback init of a library with errors
+  never reaches the cache and that entries written before the change count as
+  a miss; the serialization section of the design document follows the new
+  pickled state.
+
+- **openspec:** Update the run terminal spec for sticky scroll after a reuse ([2fb8217](https://github.com/robotcodedev/robotcode/commit/2fb821732150b8c051f120852cdffd9dc8c7feaf))
+
+  Copy Output of a run ends with the line about the reuse, and the sticky scroll
+  of a reused terminal shows only the run's command line.
+
+- **openspec:** Archive the vscode-terminal-runs-without-debug-console change ([fe33479](https://github.com/robotcodedev/robotcode/commit/fe334790fd641e1772e66c232b5160356be63d81))
+
+  Moves the change to the archive, adds the requirement for the closed Debug
+  Console to vscode-run-terminal and updates the running and debugging
+  requirement of vscode-user-guide.
+
+- **openspec:** Archive the semantic-model-hover change ([7079bc5](https://github.com/robotcodedev/robotcode/commit/7079bc5976d04bff0f2a63de3f452f4a741a4b13))
+
+  Moves the change to the archive and adds the new main spec
+  semantic-model-hover.
+
+- **openspec:** Plan restoring the keywords of a cached semantic model ([47e34db](https://github.com/robotcodedev/robotcode/commit/47e34db5f35323132032603b45d6c6aeb99279c4))
+
+  A model restored from the namespace disk cache holds copies of its
+  keywords, and BuiltIn ones lose their library, so after a restart the
+  semantic-model path offers no documentation for them until the file is
+  edited. The change stores ids for keywords and imports when the model is
+  pickled and maps them back on restore, as the design document planned.
+
+- **openspec:** Plan keeping the Debug Console closed for runs in a terminal ([d26cda1](https://github.com/robotcodedev/robotcode/commit/d26cda1f4c52da9698e543114df980c569bbdeed))
+
+  A run in a terminal stays in front: VS Code no longer switches the panel to
+  the Debug Console at the first run of a window, unless a launch configuration
+  or the user's own debug.internalConsoleOptions setting says so.
+
+- **openspec:** Complete the semantic-model-hover change ([2a47101](https://github.com/robotcodedev/robotcode/commit/2a47101f85ec36c994719ed268475f0afc78ad0e))
+
+  The change was narrowed while implementing it: hover keeps reading the
+  reference lists, so it gives the model path the documentation targets of
+  keywords in inline IF bodies and Run Keyword arguments and a parity test.
+  The plans of the switchover, the cleanup and completion and the design
+  document follow it; the granularity audit moves to completion.
+
+- **openspec:** Bring the plan for the site's media up to date ([83b98ae](https://github.com/robotcodedev/robotcode/commit/83b98aedd1af0abbd0297296a17ae1a00005d393))
+
+  The plan deletes only the dark files of the home page tour and the About page,
+  so the Mason screenshot of the Neovim page and the PyCharm screenshots of the
+  v2.8.0 news post stay. It also notes what changed since it was written: the
+  PyCharm guide's picture folder, the retaken PyCharm hover, the Halloween season,
+  and the waits the PyCharm shots need.
+
+- **openspec:** Complete the dev-builds-latest-run change ([e1cf3e6](https://github.com/robotcodedev/robotcode/commit/e1cf3e683908d60096e2263adea9ed86de8b7b06))
+
+  All tasks are done, the check of the manual publish run included; the change
+  is archived after intellij-marketplace-publish, whose requirements it modifies.
+
+- **openspec:** Archive the dev-builds-page change ([defe94a](https://github.com/robotcodedev/robotcode/commit/defe94a97aa88f53fcae40fe0a43c949c884b67c))
+
+  Moves the change to the archive and adds its requirement on the documentation
+  of the dev builds to the main spec release-publishing.
+
+- **openspec:** Update the semantic-model-hover plan to the current model ([56129a5](https://github.com/robotcodedev/robotcode/commit/56129a5394109686e8a0e235ffeda9d016c37536))
+
+  The plan now follows the model as it is: inner Run Keyword calls carry
+  KEYWORD_INNER, a variable hover covers only its name, an [Arguments] entry
+  is a PARAMETER token, and a definition is matched by its name range while
+  find_variable() serves the uses. The test case hover keeps reading its
+  documentation, tags and metadata from the test's RF node; storing them in
+  the model was rejected.
+
+- **openspec:** Complete the dev-builds-page change ([e6e8663](https://github.com/robotcodedev/robotcode/commit/e6e8663527350bb6b41876e4eb7e0626f1f3e714))
+
+  All tasks are done; the design records what the checks found while writing the page, such as how pip and uv go back from a dev version.
+
+- **openspec:** Archive the contributor-checks change ([3a0883b](https://github.com/robotcodedev/robotcode/commit/3a0883b3e1ac1a638dec2585dab6257971a9ac05))
+
+  Moves the change to the archive, adds the new main spec development-container
+  and adds the ESLint requirement to continuous-integration.
+
+- **openspec:** Archive the vscode-copy-environment-info change ([909be3b](https://github.com/robotcodedev/robotcode/commit/909be3b5d8d421fc1e76bf93d0af5901cb42b001))
+
+  Moves the change to the archive, adds the new main spec vscode-environment-info
+  and updates the troubleshooting requirement of vscode-user-guide.
+
+- **openspec:** Plan a page about the dev builds ([4d56474](https://github.com/robotcodedev/robotcode/commit/4d56474a72141249e45111813414af7004d8c4ef))
+- **openspec:** Plan ESLint in the CI and the test tools in the dev container ([a8f0cbc](https://github.com/robotcodedev/robotcode/commit/a8f0cbc9d386cbfab271ccbbdd6fcedbc53079b7))
+- **openspec:** Archive the intellij-python-interpreter change ([ec14566](https://github.com/robotcodedev/robotcode/commit/ec14566c0ca99253839f679f195398b8c550117b))
+
+  Moves the change to the archive and adds its requirements on the module
+  choice to the main spec intellij-python-environment, and those on the
+  checks before a run, including remote interpreters in the editor, to
+  intellij-run-configurations.
+
+- **openspec:** Plan copying the environment info in VS Code ([50a4345](https://github.com/robotcodedev/robotcode/commit/50a434508a76c67d50c9c103b2049bf9b19c153b))
+
+  A command copies the versions of a workspace folder as a list for an issue,
+  a forum post or a chat, also from the RobotCode menu (#260).
+
+- **openspec:** Archive the pypi-dev-builds change ([4f2003c](https://github.com/robotcodedev/robotcode/commit/4f2003c7c0c9eb8c3f53f01c81e3a5d5aa6c43a4))
+
+  Moves the change to the archive and adds its requirements on the nightly dev
+  builds of the Python packages to the main spec release-publishing.
+
+- **openspec:** Plan conditions on the debugger's exception filters ([4d93a56](https://github.com/robotcodedev/robotcode/commit/4d93a56078fac267b65bda76ae811f0b5d0f2a0e))
+
+  The debugger is to honor the condition that VS Code lets the user set on
+  "Failed Keywords", "Uncaught Failed Keywords", "Failed Tests" and "Failed
+  Suites", and to offer the name and the message of the failure to it as
+  ${EXCEPTION_NAME} and ${EXCEPTION_MESSAGE}.
+
 - **openspec:** Archive the vscode-new-documentation-viewer change ([84923c6](https://github.com/robotcodedev/robotcode/commit/84923c69ed5d32b90b0d7644f0ac76f8b4fa09c9))
 
   Moves the change to the archive and brings the main spec
@@ -2378,6 +2584,10 @@ All notable changes to this project will be documented in this file. See [conven
 
   Adds a VS Code section to the page about browsing documentation, and the installation table now says that `robotcode doc` and the Documentation Viewer do not need Python-Markdown.
 
+- **website:** Add a page on how to try the dev builds ([a4eb6b7](https://github.com/robotcodedev/robotcode/commit/a4eb6b7eec85dc3a46a994374d5f1a3419719f09))
+
+  The new Getting Started page explains how to switch to the dev builds of the VS Code extension, the PyCharm plugin and the Python packages, with pip or uv, how to recognize them and how to go back to a release. The README links it under Get Involved.
+
 - **website:** Let the Halloween fog and the Spooky switch move in steps ([75e2040](https://github.com/robotcodedev/robotcode/commit/75e2040147d59eae546619eaedb21b00914b1743))
 
   The fog drifts and billows in small steps and the floating Spooky

{robotcode-2.8.0.dev631 → robotcode-2.8.0.dev670}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: robotcode
-Version: 2.8.0-dev.631
+Version: 2.8.0-dev.670
 Summary: Command line interface for RobotCode
 Project-URL: Homepage, https://robotcode.io
 Project-URL: Donate, https://opencollective.com/robotcode
@@ -34,35 +34,35 @@ Classifier: Topic :: Text Editors :: Integrated Development Environments (IDE)
 Classifier: Topic :: Utilities
 Classifier: Typing :: Typed
 Requires-Python: >=3.10
-Requires-Dist: robotcode-core==2.8.0-dev.631
-Requires-Dist: robotcode-plugin==2.8.0-dev.631
-Requires-Dist: robotcode-robot==2.8.0-dev.631
+Requires-Dist: robotcode-core==2.8.0-dev.670
+Requires-Dist: robotcode-plugin==2.8.0-dev.670
+Requires-Dist: robotcode-robot==2.8.0-dev.670
 Provides-Extra: all
 Requires-Dist: docutils; extra == 'all'
 Requires-Dist: pyyaml>=5.4; extra == 'all'
-Requires-Dist: robotcode-analyze==2.8.0-dev.631; extra == 'all'
-Requires-Dist: robotcode-debugger==2.8.0-dev.631; extra == 'all'
-Requires-Dist: robotcode-language-server==2.8.0-dev.631; extra == 'all'
-Requires-Dist: robotcode-repl-server==2.8.0-dev.631; extra == 'all'
-Requires-Dist: robotcode-repl==2.8.0-dev.631; extra == 'all'
-Requires-Dist: robotcode-runner==2.8.0-dev.631; extra == 'all'
+Requires-Dist: robotcode-analyze==2.8.0-dev.670; extra == 'all'
+Requires-Dist: robotcode-debugger==2.8.0-dev.670; extra == 'all'
+Requires-Dist: robotcode-language-server==2.8.0-dev.670; extra == 'all'
+Requires-Dist: robotcode-repl-server==2.8.0-dev.670; extra == 'all'
+Requires-Dist: robotcode-repl==2.8.0-dev.670; extra == 'all'
+Requires-Dist: robotcode-runner==2.8.0-dev.670; extra == 'all'
 Requires-Dist: robotframework-robocop>=6.0.0; extra == 'all'
 Provides-Extra: analyze
-Requires-Dist: robotcode-analyze==2.8.0-dev.631; extra == 'analyze'
+Requires-Dist: robotcode-analyze==2.8.0-dev.670; extra == 'analyze'
 Provides-Extra: debugger
-Requires-Dist: robotcode-debugger==2.8.0-dev.631; extra == 'debugger'
+Requires-Dist: robotcode-debugger==2.8.0-dev.670; extra == 'debugger'
 Provides-Extra: languageserver
-Requires-Dist: robotcode-language-server==2.8.0-dev.631; extra == 'languageserver'
+Requires-Dist: robotcode-language-server==2.8.0-dev.670; extra == 'languageserver'
 Provides-Extra: lint
 Requires-Dist: robotframework-robocop>=2.0.0; extra == 'lint'
 Provides-Extra: repl
-Requires-Dist: robotcode-repl==2.8.0-dev.631; extra == 'repl'
+Requires-Dist: robotcode-repl==2.8.0-dev.670; extra == 'repl'
 Provides-Extra: replserver
-Requires-Dist: robotcode-repl-server==2.8.0-dev.631; extra == 'replserver'
+Requires-Dist: robotcode-repl-server==2.8.0-dev.670; extra == 'replserver'
 Provides-Extra: rest
 Requires-Dist: docutils; extra == 'rest'
 Provides-Extra: runner
-Requires-Dist: robotcode-runner==2.8.0-dev.631; extra == 'runner'
+Requires-Dist: robotcode-runner==2.8.0-dev.670; extra == 'runner'
 Provides-Extra: yaml
 Requires-Dist: pyyaml>=5.4; extra == 'yaml'
 Description-Content-Type: text/markdown
@@ -220,6 +220,7 @@ You don't need to sponsor to help. Every contribution — feedback, code, advoca
 - Leave a review on the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=d-biehl.robotcode) and [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/26216)
 - Ask questions & help others on [Slack #robotcode](https://slack.robotframework.org/), the [Forum](https://forum.robotframework.org), or [Discussions](https://github.com/robotcodedev/robotcode/discussions)
 - Report bugs in the [issue tracker](https://github.com/robotcodedev/robotcode/issues)
+- Try the [dev builds](https://robotcode.io/getting-started/dev-builds/) and report what you find
 - Suggest enhancements or features (issues or [Discussions](https://github.com/robotcodedev/robotcode/discussions))
 - Share usage patterns & integration ideas in [Discussions](https://github.com/robotcodedev/robotcode/discussions)
 - Improve tests (edge cases, large suites, multi-root, versions)

{robotcode-2.8.0.dev631 → robotcode-2.8.0.dev670}/README.md

@@ -151,6 +151,7 @@ You don't need to sponsor to help. Every contribution — feedback, code, advoca
 - Leave a review on the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=d-biehl.robotcode) and [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/26216)
 - Ask questions & help others on [Slack #robotcode](https://slack.robotframework.org/), the [Forum](https://forum.robotframework.org), or [Discussions](https://github.com/robotcodedev/robotcode/discussions)
 - Report bugs in the [issue tracker](https://github.com/robotcodedev/robotcode/issues)
+- Try the [dev builds](https://robotcode.io/getting-started/dev-builds/) and report what you find
 - Suggest enhancements or features (issues or [Discussions](https://github.com/robotcodedev/robotcode/discussions))
 - Share usage patterns & integration ideas in [Discussions](https://github.com/robotcodedev/robotcode/discussions)
 - Improve tests (edge cases, large suites, multi-root, versions)

{robotcode-2.8.0.dev631 → robotcode-2.8.0.dev670}/pyproject.toml

@@ -49,26 +49,26 @@ classifiers = [
   "Framework :: Robot Framework :: Tool",
 ]
 requires-python = ">=3.10"
-dependencies = ["robotcode-core==2.8.0-dev.631", "robotcode-plugin==2.8.0-dev.631", "robotcode-robot==2.8.0-dev.631"]
+dependencies = ["robotcode-core==2.8.0-dev.670", "robotcode-plugin==2.8.0-dev.670", "robotcode-robot==2.8.0-dev.670"]
 dynamic = ["version"]
 
 [project.optional-dependencies]
-debugger = ["robotcode-debugger==2.8.0-dev.631"]
-languageserver = ["robotcode-language-server==2.8.0-dev.631"]
-runner = ["robotcode-runner==2.8.0-dev.631"]
-analyze = ["robotcode-analyze==2.8.0-dev.631"]
+debugger = ["robotcode-debugger==2.8.0-dev.670"]
+languageserver = ["robotcode-language-server==2.8.0-dev.670"]
+runner = ["robotcode-runner==2.8.0-dev.670"]
+analyze = ["robotcode-analyze==2.8.0-dev.670"]
 yaml = ["PyYAML>=5.4"]
 lint = ["robotframework-robocop>=2.0.0"]
 rest = ["docutils"]
-repl = ["robotcode-repl==2.8.0-dev.631"]
-replserver = ["robotcode-repl-server==2.8.0-dev.631"]
+repl = ["robotcode-repl==2.8.0-dev.670"]
+replserver = ["robotcode-repl-server==2.8.0-dev.670"]
 all = [
-  "robotcode-debugger==2.8.0-dev.631",
-  "robotcode-language-server==2.8.0-dev.631",
-  "robotcode-runner==2.8.0-dev.631",
-  "robotcode-analyze==2.8.0-dev.631",
-  "robotcode-repl==2.8.0-dev.631",
-  "robotcode-repl-server==2.8.0-dev.631",
+  "robotcode-debugger==2.8.0-dev.670",
+  "robotcode-language-server==2.8.0-dev.670",
+  "robotcode-runner==2.8.0-dev.670",
+  "robotcode-analyze==2.8.0-dev.670",
+  "robotcode-repl==2.8.0-dev.670",
+  "robotcode-repl-server==2.8.0-dev.670",
   "PyYAML>=5.4",
   "robotframework-robocop>=6.0.0",
   "docutils"

robotcode-2.8.0.dev670/src/robotcode/cli/__version__.py

@@ -0,0 +1 @@
+__version__ = "2.8.0-dev.670"

robotcode-2.8.0.dev631/src/robotcode/cli/__version__.py

@@ -1 +0,0 @@
-__version__ = "2.8.0-dev.631"