Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lock file maintenance Node dependencies #816

Merged
merged 1 commit into from May 11, 2024
Merged

Lock file maintenance Node dependencies #816

merged 1 commit into from May 11, 2024

Conversation

ggrossetie
Copy link
Member

@ggrossetie ggrossetie commented Nov 6, 2023 •
edited

This PR contains the following updates:

Package Type Update Change
lockFileMaintenance All locks refreshed
@asciidoctor/core dependencies patch 2.2.6 -> 2.2.7
@highlightjs/cdn-assets (source) devDependencies minor ~11.8.0 -> ~11.9.0
@playwright/test (source) devDependencies minor ~1.41 -> ~1.44.0
@types/vscode devDependencies minor ~1.75 -> ~1.89.0
@vscode/vsce (source) devDependencies minor 2.23.0 -> 2.26.1
eslint (source) devDependencies minor 8.48.0 -> 8.57.0
eslint-plugin-import devDependencies minor 2.28.1 -> 2.29.1
mocha (source) devDependencies minor 10.2.0 -> 10.4.0
node volta minor 18.17.1 -> 18.20.2
ts-loader devDependencies minor 9.4.4 -> 9.5.1
webpack devDependencies minor 5.88.2 -> 5.91.0

πŸ”§ This Pull Request updates lock files to use the latest dependency versions.

Release Notes

asciidoctor/asciidoctor.js

v2.2.7

Compare Source

Summary

This release is based on Asciidoctor 2.0.22 and Opal 0.11.99.dev (31d26d69).

Release meta

Released on: 2024-03-17
Released by: @​ggrossetie
Published by: GitHub Actions

Logs: full diff

What's Changed
highlightjs/highlight.js

v11.9.0

Compare Source

CAVEATS / POTENTIALLY BREAKING CHANGES

  • Drops support for Node 14.x, which is no longer supported by Node.js.
  • In the node build styles/*.css files now ship un-minified
    with minified counterparts as: styles/*.min.css mvorisek
    (this makes things consistent with our cdn builds)

Parser:

  • (enh) prevent re-highlighting of an element [joshgoebel][]
  • (chore) Remove discontinued badges from README Bradley Mackey
  • (chore) Fix build size report Bradley Mackey

New Grammars:

  • added 3rd party Iptables grammar to SUPPORTED_LANGUAGES Checconio
  • added 3rd party x86asmatt grammar to SUPPORTED_LANGUAGES gondow
  • added 3rd party riscv64 grammar to SUPPORTED_LANGUAGES aana-h2
  • added 3rd party Ballerina grammar to SUPPORTED_LANGUAGES Yasith Deelaka

Core Grammars:

  • fix(cpp) fixed highlighter break state Md Saad Akhtar
  • fix(rust) added negative-lookahead for callable keywords if while for [Omar Hussein][]
  • enh(armasm) added x0-x30 and w0-w30 ARMv8 registers Nicholas Thompson
  • enh(haxe) added final, is, macro keywords and `This PR contains the following updates:
Package Type Update Change
lockFileMaintenance All locks refreshed
@asciidoctor/core dependencies patch 2.2.6 -> 2.2.7
@highlightjs/cdn-assets (source) devDependencies minor ~11.8.0 -> ~11.9.0
@playwright/test (source) devDependencies minor ~1.41 -> ~1.44.0
@types/vscode devDependencies minor ~1.75 -> ~1.89.0
@vscode/vsce (source) devDependencies minor 2.23.0 -> 2.26.1
eslint (source) devDependencies minor 8.48.0 -> 8.57.0
eslint-plugin-import devDependencies minor 2.28.1 -> 2.29.1
mocha (source) devDependencies minor 10.2.0 -> 10.4.0
node volta minor 18.17.1 -> 18.20.2
ts-loader devDependencies minor 9.4.4 -> 9.5.1
webpack devDependencies minor 5.88.2 -> 5.91.0

πŸ”§ This Pull Request updates lock files to use the latest dependency versions.

identifiers Robert Borghese

  • enh(haxe) support numeric separators and suffixes Robert Borghese
  • fix(haxe) fixed metadata arguments and support non-colon syntax Robert Borghese
  • fix(haxe) differentiate abstract declaration from keyword Robert Borghese
  • fix(bash) do not delimit a string by an escaped apostrophe [hancar][]
  • enh(swift) support macro keyword Bradley Mackey
  • enh(swift) support parameter pack keywords Bradley Mackey
  • enh(swift) regex literal support Bradley Mackey
  • enh(swift) @unchecked and @Sendable support Bradley Mackey
  • enh(scala) add using directives support //> using foo bar [Jamie Thompson][]
  • fix(scala) fixed comments in constructor arguments not being properly highlighted Isaac Nonato
  • enh(swift) ownership modifiers support Bradley Mackey
  • enh(nsis) Add !assert compiler flag [idleberg][]
  • fix(haskell) do not treat double dashes inside infix operators as comments [Zlondrej][]
  • enh(rust) added eprintln! macro qoheniac
  • enh(leaf) update syntax to 4.0 Samuel Bishop
  • fix(reasonml) simplify syntax and align it with ocaml jchavarri
  • fix(swift) warn_unqualified_access is an attribute Bradley Mackey
  • enh(swift) macro attributes are highlighted as keywords Bradley Mackey
  • enh(stan) updated for version 2.33 (#​3859) Brian Ward
  • enh(llvm) match additional types wtz
  • fix(css) added '_' css variable detection Md Saad Akhtar
  • enh(groovy) add record and var as keywords Guillaume Laforge

Developer Tool:

microsoft/playwright

v1.44.0

Compare Source

New APIs

Accessibility assertions

  • expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

    const locator = page.getByRole('button');
await expect(locator).toHaveAccessibleName('Submit');

  • expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

    const locator = page.getByRole('button');
await expect(locator).toHaveAccessibleDescription('Upload a photo');

  • expect(locator).toHaveRole() checks if the element has the specified ARIA role:

    const locator = page.getByTestId('save-button');
await expect(locator).toHaveRole('button');

Locator handler

  • After executing the handler added with page.addLocatorHandler(), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new noWaitAfter option.
  • You can use new times option in page.addLocatorHandler() to specify maximum number of times the handler should be run.
  • The handler in page.addLocatorHandler() now accepts the locator as argument.
  • New page.removeLocatorHandler() method for removing previously added locator handlers.
const locator = page.getByText('This interstitial covers the button');
await page.addLocatorHandler(locator, async overlay => {
  await overlay.locator('#close').click();
}, { times: 3, noWaitAfter: true });
// Run your tests that can be interrupted by the overlay.
// ...
await page.removeLocatorHandler(locator);

Miscellaneous options

  • multipart option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

    const formData = new FormData();
formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' }));
formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' }));
context.request.post('https://example.com/uploadFiles', {
  multipart: formData
});

  • expect(callback).toPass({ intervals }) can now be configured by expect.toPass.inervals option globally in testConfig.expect or per project in testProject.expect.

  • expect(page).toHaveURL(url) now supports ignoreCase option.

  • testProject.ignoreSnapshots allows to configure per project whether to skip screenshot expectations.

Reporter API

  • New method suite.entries() returns child test suites and test cases in their declaration order. suite.type and testCase.type can be used to tell apart test cases and suites in the list.
  • Blob reporter now allows overriding report file path with a single option outputFile. The same option can also be specified as PLAYWRIGHT_BLOB_OUTPUT_FILE environment variable that might be more convenient on CI/CD.
  • JUnit reporter now supports includeProjectInTestName option.

Command line

  • --last-failed CLI option for running only tests that failed in the previous run.

    First run all tests:

    $ npx playwright test

Running 103 tests using 5 workers
...
2 failed
  [chromium] β€Ί my-test.spec.ts:8:5 β€Ί two ─────────────────────────────────────────────────────────
  [chromium] β€Ί my-test.spec.ts:13:5 β€Ί three ──────────────────────────────────────────────────────
101 passed (30.0s)

    Now fix the failing tests and run Playwright again with --last-failed option:

    $ npx playwright test --last-failed

Running 2 tests using 2 workers
  2 passed (1.2s)

Browser Versions

  • Chromium 125.0.6422.14
  • Mozilla Firefox 125.0.1
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 124
  • Microsoft Edge 124

v1.43.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/30300 - [REGRESSION]: UI mode restarts if keep storage statehttps://github.com/microsoft/playwright/issues/303399 - [REGRESSION]: Brand new install of playwright, unable to run chromium with show browser using vscode

Browser Versions
  • Chromium 124.0.6367.29
  • Mozilla Firefox 124.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 123
  • Microsoft Edge 123

v1.43.0

Compare Source

New APIs

  • Method browserContext.clearCookies() now supports filters to remove only some cookies.

    // Clear all cookies.
await context.clearCookies();
// New: clear cookies with a particular name.
await context.clearCookies({ name: 'session-id' });
// New: clear cookies for a particular domain.
await context.clearCookies({ domain: 'my-origin.com' });

  • New mode retain-on-first-failure for testOptions.trace. In this mode, trace is recorded for the first run of each test, but not for retires. When test run fails, the trace file is retained, otherwise it is removed.

    import { defineConfig } from '@​playwright/test';

export default defineConfig({
  use: {
    trace: 'retain-on-first-failure',
  },
});

  • New property testInfo.tags exposes test tags during test execution.

    test('example', async ({ page }) => {
  console.log(test.info().tags);
});

  • New method locator.contentFrame() converts a Locator object to a FrameLocator. This can be useful when you have a Locator object obtained somewhere, and later on would like to interact with the content inside the frame.

    const locator = page.locator('iframe[name="embedded"]');
// ...
const frameLocator = locator.contentFrame();
await frameLocator.getByRole('button').click();

  • New method frameLocator.owner() converts a FrameLocator object to a Locator. This can be useful when you have a FrameLocator object obtained somewhere, and later on would like to interact with the iframe element.

    const frameLocator = page.frameLocator('iframe[name="embedded"]');
// ...
const locator = frameLocator.owner();
await expect(locator).toBeVisible();

UI Mode Updates

Playwright UI Mode

  • See tags in the test list.
  • Filter by tags by typing @fast or clicking on the tag itself.
  • New shortcuts:
    • F5 to run tests.
    • Shift F5 to stop running tests.
    • Ctrl ` to toggle test output.

Browser Versions

  • Chromium 124.0.6367.29
  • Mozilla Firefox 124.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 123
  • Microsoft Edge 123

v1.42.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29732 - [Regression]: HEAD requests to webServer.url since v1.42.0https://github.com/microsoft/playwright/issues/297466 - [Regression]: Playwright CT CLI scripts fail due to broken initializePlugin imporhttps://github.com/microsoft/playwright/issues/2973939 - [Bug]: Component tests fails when imported a module with a dot in a nahttps://github.com/microsoft/playwright/issues/29731731 - [Regression]: 1.42.0 breaks some import statemehttps://github.com/microsoft/playwright/issues/297609760 - [Bug]: Possible regression with chained locators in v1.42

Browser Versions
  • Chromium 123.0.6312.4
  • Mozilla Firefox 123.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 122
  • Microsoft Edge 123

v1.42.0

Compare Source

New APIs

  • Test tags

    New tag syntax for adding tags to the tests (@​-tokens in the test title are still supported).

    test('test customer login', { tag: ['@​fast', '@​login'] }, async ({ page }) => {
  // ...
});

    Use --grep command line option to run only tests with certain tags.

    npx playwright test --grep @​fast

  • Annotating skipped tests

    New annotation syntax for test annotations allows annotating the tests that do not run.

    test('test full report', {
  annotation: [
    { type: 'issue', description: 'https://github.com/microsoft/playwright/issues/23180' },
    { type: 'docs', description: 'https://playwright.dev/docs/test-annotations#tag-tests' },
  ],
}, async ({ page }) => {
  // ...
});

  • page.addLocatorHandler()

[!WARNING]
This feature is experimental, we are actively looking for the feedback based on your scenarios.

New method page.addLocatorHandler() registers a callback that will be invoked when specified element becomes visible and may block Playwright actions. The callback can get rid of the overlay. Here is an example that closes a cookie dialog when it appears.

// Setup the handler.
await page.addLocatorHandler(
    page.getByRole('heading', { name: 'Hej! You are in control of your cookies.' }),
    async () => {
      await page.getByRole('button', { name: 'Accept all' }).click();
    });
// Write the test as usual.
await page.goto('https://www.ikea.com/');
await page.getByRole('link', { name: 'Collection of blue and white' }).click();
await expect(page.getByRole('heading', { name: 'Light and easy' })).toBeVisible();

  • Project wildcard filter
    Playwright command line flag now supports '*' wildcard when filtering by project.

    npx playwright test --project='*mobile*'

  • Other APIs

    • expect(callback).toPass({ timeout })
      The timeout can now be configured by expect.toPass.timeout option globally or in project config

    • electronApplication.on('console')
      electronApplication.on('console') event is emitted when Electron main process calls console API methods.

      electronApp.on('console', async msg => {
  const values = [];
  for (const arg of msg.args())
    values.push(await arg.jsonValue());
  console.log(...values);
});
await electronApp.evaluate(() => console.log('hello', 5, { foo: 'bar' }));

    • page.pdf() accepts two new options tagged and outline.

Breaking changes

Mixing the test instances in the same suite is no longer supported. Allowing it was an oversight as it makes reasoning about the semantics unnecessarily hard.

const test = baseTest.extend({ item: async ({}, use) => {} });
baseTest.describe('Admin user', () => {
  test('1', async ({ page, item }) => {});
  test('2', async ({ page, item }) => {});
});

Announcements

  • ⚠️ Ubuntu 18 is not supported anymore.

Browser Versions

  • Chromium 123.0.6312.4
  • Mozilla Firefox 123.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 122
  • Microsoft Edge 123
Microsoft/vsce

v2.26.1

Compare Source

Changes:

Feature Requests:
Others:

This list of changes was auto generated.

v2.26.0

Compare Source

Changes:

Feature Requests:
  • #​964: Add --azure-credential option to "publish", "unpublish" and "verify-pat" commands
  • #​943: feat: ignore .git generated by git worktree add
  • #​966: allow verifyPat to use extension's publisher name
Others:

v2.25.0

Compare Source

Full Changelog: microsoft/vscode-vsce@v2.25.0...v2.25.0

What's Changed

⚠️ Node engine version has been bumped up from >=14 to >=16

New Contributors

Full Changelog: microsoft/vscode-vsce@v2.24.0...v2.25.0

v2.24.0

Compare Source

eslint/eslint

v8.57.0

Compare Source

Features

Bug Fixes

Documentation

Chores

v8.56.0

Compare Source

Features

  • 0dd9704 feat: Support custom severity when reporting unused disable directives (#​17212) (Bryan Mishkin)
  • 31a7e3f feat: fix no-restricted-properties false negatives with unknown objects (#​17818) (Arka Pratim Chaudhuri)

Bug Fixes

  • 7d5e5f6 fix: TypeError: fs.exists is not a function on read-only file system (#​17846) (Francesco Trotta)
  • 74739c8 fix: suggestion with invalid syntax in no-promise-executor-return rule (#​17812) (Bryan Mishkin)

Documentation

Chores

v8.55.0

Compare Source

Features

Documentation

Chores

v8.54.0

Compare Source

Features

Bug Fixes

  • 98926e6 fix: Ensure that extra data is not accidentally stored in the cache file (#​17760) (Milos Djermanovic)
  • e8cf9f6 fix: Make dark scroll bar in dark theme (#​17753) (Pavel)
  • 3cbeaad fix: Use cwd constructor option as config basePath in Linter (#​17705) (Milos Djermanovic)

Documentation

Chores

v8.53.0

Compare Source

Features

Bug Fixes

  • 1ad6257 fix: ensure that exit code for fatal errors is not overwritten (#​17683) (Milos Djermanovic)
  • b329ea7 fix: add ; after JSX nodes in no-object-constructor autofix (#​17672) (Francesco Trotta)

Documentation

Chores

v8.52.0

Compare Source

Features

  • 70648ee feat: report-unused-disable-directive to report unused eslint-enable (#​17611) (Yosuke Ota)

Bug Fixes

  • 5de9637 fix: Ensure shared references in rule configs are separated (#​17666) (Nicholas C. Zakas)
  • dcfe573 fix: add preceding semicolon in suggestions of no-object-constructor (#​17649) (Francesco Trotta)

Documentation

Chores

v8.51.0

Compare Source

Features

  • 0a9c433 feat: Add --no-warn-ignored CLI option for flat config (#​17569) (Domantas Petrauskas)
  • 977e67e feat: logical-assignment-operators to report expressions with 3 operands (#​17600) (Yosuke Ota)

Bug Fixes

  • f976b2f fix: make rule severity case-sensitive in flat config (#​17619) (Milos Djermanovic)
  • 0edfe36 fix: Ensure crash error messages are not duplicated (#​17584) (Nicholas C. Zakas)
  • dd79abc fix: eslint-disable to be able to parse quoted rule names (#​17612) (Yosuke Ota)
  • d2f6801 fix: Ensure correct code path for && followed by ?? (#​17618) (Nicholas C. Zakas)

Documentation

Chores

v8.50.0

Compare Source

Features

Bug Fixes

  • cc4d26b fix: Ensure deprecated context.parserServices warns (#​17593) (Nicholas C. Zakas)
  • 1ea4cfb fix: Ensure all RuleTester tests all deprecated context methods (#​17587) (Nicholas C. Zakas)
  • aa1b657 fix: wrong suggestion and message in no-misleading-character-class (#​17571) (Yosuke Ota)

Documentation

Chores

v8.49.0

Compare Source

Features

Documentation

Chores

Configuration

πŸ“… Schedule: "before 5am on monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ‘» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 3 times, most recently from e91e7fc to fc819a4 Compare November 18, 2023 02:19
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 5 times, most recently from 6aa9680 to 6429faa Compare November 26, 2023 02:20
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 30d8c50 to 2d7ec21 Compare December 2, 2023 02:20
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 9f12ac8 to 4c24a98 Compare December 15, 2023 02:22
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 6ada073 to 84f1cdd Compare December 20, 2023 02:11
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 6094d42 to 91c7c47 Compare January 27, 2024 02:13
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 5f0ee78 to 4feb207 Compare February 4, 2024 02:15
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 3 times, most recently from 412c548 to 0975908 Compare February 15, 2024 02:15
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 65ffbd1 to c0ec85b Compare February 20, 2024 02:12
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 3 times, most recently from bbc5118 to 336d729 Compare February 29, 2024 02:11
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 3 times, most recently from 7383a81 to b40adbc Compare March 23, 2024 02:13
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from c5f2f33 to 90f37db Compare March 27, 2024 02:14
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 0097d80 to 7999fc3 Compare April 5, 2024 02:15
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from 028a012 to b4b5374 Compare April 13, 2024 02:09
@ggrossetie ggrossetie force-pushed the renovate/node-dependencies branch 2 times, most recently from e259aa0 to e114f4a Compare May 4, 2024 02:16
@ggrossetie ggrossetie merged commit 41139c9 into master May 11, 2024
2 checks passed
@ggrossetie ggrossetie deleted the renovate/node-dependencies branch May 11, 2024 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@ggrossetie