[pull] master from robotframework:master#145
Open
pull[bot] wants to merge 1876 commits intotestautomation:masterfrom
Open
[pull] master from robotframework:master#145pull[bot] wants to merge 1876 commits intotestautomation:masterfrom
pull[bot] wants to merge 1876 commits intotestautomation:masterfrom
Conversation
Manage this branch in SquashTest this branch here: https://master-n02a3.squash.io |
Removed the installation and execution of rflogs from the workflow.
Removed archiving of acceptance test results and rflogs installation.
Add step to archive acceptance test results on failure.
This avoids warnings when #5492 is implemented.
This makes it possible to show source and line number in import errors/warnings also when using `Import Library/Resource/Variables` keywords for importing libraries. Need by #5492.
Libraries imported with the same name as already imported libraries are ignored. This used to be silent, but after this commit there are warnings in these cases: - Library is re-imported with different arguments than earlier. - Library is imported using an alias that is used by another imported library. Fixes #5492.
Remove class references from docs when method has a return type.
- Run tests also with Python 3.14 (#5435). Hopefully using just '3.14' is enough when it's still in the RC phase. - Run unit tests with PRs with same Python versions as acceptance tests.
Trying to setup running tests with Python 3.14 on GitHub Actions (#5435). Using '3.14' as the version didn't work, because Python 3.14 is still in the RC phase. Using '3.14-dev' ought give us the latest preview release (and hopefully the final version vhen it's released): https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#using-the-python-version-input
In practice using
VAR ${scalar} scope=TEST
will cause a deprecation warning and should be replaced with
VAR ${scalar} ${EMPTY} scope=TEST
No changes to creating @{list} and &{dict} variables or when using the
local scope implicitly or explicitly.
Fixes #5439.
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.6.0 to 6.0.0. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v5.6.0...v6.0.0) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 5. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Most importantly, try to fix tests on Windows.
Part of issue #5373. --------- Co-authored-by: Clemens Otto <clemens.otto@rohde-schwarz.com>
Values were already validated by keywords themselves so there are no real functional changes. The main benefit is getting the accepted values shown automatically in documentation and in some cases also error messages got better. In the future IDEs may also be able to auto-complete the accepted values. Existing argument validation wasn't removed from keywords to avoid problems in programmatic usage. This is related to adding typing to standard libraries (#5373).
Main motivation is making it easier to add Markdown support (#5304) later. Also enhance related tests a bit.
Anchore generated by Libdoc is uppercase `Introduction`, header id should match that. Fixes #5601
See #5597. Co-authored-by: Marvin Klerx <marvin.klerx.ext@siemens.com>
Notes are mostly simplified. Fixes #5597.
Also mention in installation instructions that although core features have no dependencies, individual features may have. Fixes #5590.
Bumps the npm_and_yarn group with 2 updates in the /src/web directory: [@parcel/reporter-dev-server](https://github.com/parcel-bundler/parcel) and [minimatch](https://github.com/isaacs/minimatch). Updates `@parcel/reporter-dev-server` from 2.16.0 to 2.16.4 - [Release notes](https://github.com/parcel-bundler/parcel/releases) - [Changelog](https://github.com/parcel-bundler/parcel/blob/v2/CHANGELOG.md) - [Commits](parcel-bundler/parcel@v2.16.0...v2.16.4) Updates `minimatch` from 3.1.2 to 3.1.5 - [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md) - [Commits](isaacs/minimatch@v3.1.2...v3.1.5) --- updated-dependencies: - dependency-name: "@parcel/reporter-dev-server" dependency-version: 2.16.4 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: minimatch dependency-version: 3.1.5 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
Secret variable has a special meaning nowadays.
Instead of failing for AttributeError in `_normalize`, raise explicit KeyError if getting or deleting and TypeError if setting. Fixes #5620 i.e. accessing variables returned by `BuiltIn.get_variables` with non-string keys.
Such an import would fail anyway and in some contexts the failure is really strange. Fixes #5615.
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 6 to 7. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v6...v7) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…src/web/npm_and_yarn-be23461eb3 Bump the npm_and_yarn group across 1 directory with 2 updates
Basic functionality done and tested. Various activated plugins still need to be tested separately and documentation is also totally missing. The first part of #5304.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
13 participants
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )