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

chore(deps): update all dependencies #111

Merged
merged 1 commit into from
Mar 1, 2024
Merged

chore(deps): update all dependencies #111

merged 1 commit into from
Mar 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) 7.23.9 -> 7.24.0 age adoption passing confidence
@commitlint/cli (source) 18.6.0 -> 19.0.3 age adoption passing confidence
@commitlint/config-conventional (source) 18.6.0 -> 19.0.3 age adoption passing confidence
@mantine/core (source) 7.5.1 -> 7.6.1 age adoption passing confidence
@mantine/hooks (source) 7.5.1 -> 7.6.1 age adoption passing confidence
@playwright/test (source) 1.41.2 -> 1.42.0 age adoption passing confidence
@reduxjs/toolkit (source) 2.1.0 -> 2.2.1 age adoption passing confidence
@tanstack/react-query (source) 5.18.1 -> 5.24.1 age adoption passing confidence
@tanstack/react-query-devtools (source) 5.18.1 -> 5.24.1 age adoption passing confidence
@types/react (source) 18.2.55 -> 18.2.61 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 6.21.0 -> 7.1.0 age adoption passing confidence
@typescript-eslint/parser (source) 6.21.0 -> 7.1.0 age adoption passing confidence
@vitest/ui (source) 1.2.2 -> 1.3.1 age adoption passing confidence
eslint (source) 8.56.0 -> 8.57.0 age adoption passing confidence
eslint-plugin-playwright 0.22.2 -> 1.5.1 age adoption passing confidence
husky 9.0.10 -> 9.0.11 age adoption passing confidence
react-router-dom (source) 6.22.0 -> 6.22.2 age adoption passing confidence
type-fest 4.10.2 -> 4.10.3 age adoption passing confidence
vite (source) 5.0.12 -> 5.1.4 age adoption passing confidence
vitest (source) 1.2.2 -> 1.3.1 age adoption passing confidence

Release Notes

babel/babel (@​babel/core)

v7.24.0

Compare Source

🚀 New Feature
  • babel-standalone
  • babel-core, babel-helper-create-class-features-plugin, babel-helpers, babel-plugin-transform-class-properties
  • babel-helper-create-class-features-plugin, babel-helpers, babel-plugin-proposal-decorators, babel-plugin-proposal-pipeline-operator, babel-plugin-syntax-decorators, babel-plugin-transform-class-properties, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-preset-flow
  • babel-helper-import-to-platform-api, babel-plugin-proposal-import-wasm-source, babel-plugin-proposal-json-modules, babel-standalone
  • babel-plugin-transform-runtime
  • babel-parser, babel-types
🐛 Bug Fix
  • babel-plugin-proposal-do-expressions, babel-traverse
  • babel-helper-create-class-features-plugin, babel-plugin-transform-private-methods, babel-plugin-transform-private-property-in-object
  • babel-helper-create-class-features-plugin, babel-plugin-transform-private-methods
  • babel-helper-create-class-features-plugin, babel-helpers, babel-plugin-proposal-decorators
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators, babel-plugin-transform-async-generator-functions, babel-plugin-transform-private-methods, babel-plugin-transform-private-property-in-object, babel-plugin-transform-typescript, babel-preset-env
  • babel-helpers
  • babel-helpers, babel-plugin-proposal-decorators
💅 Polish
  • babel-core, babel-helper-create-class-features-plugin, babel-preset-env
🏠 Internal
🔬 Output optimization
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
  • babel-helper-create-class-features-plugin, babel-helpers, babel-plugin-proposal-decorators, babel-plugin-proposal-pipeline-operator, babel-plugin-transform-class-properties
  • babel-helper-create-class-features-plugin, babel-helpers, babel-plugin-transform-private-methods
  • babel-helper-create-class-features-plugin, babel-helpers, babel-plugin-proposal-decorators
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties
  • babel-helper-create-class-features-plugin, babel-helper-fixtures, babel-helpers, babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-proposal-decorators, babel-plugin-proposal-destructuring-private, babel-plugin-proposal-optional-chaining-assign, babel-plugin-transform-class-properties, babel-plugin-transform-class-static-block, babel-plugin-transform-private-methods, babel-plugin-transform-private-property-in-object, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-helpers, babel-plugin-proposal-decorators
conventional-changelog/commitlint (@​commitlint/cli)

v19.0.3

Compare Source

Note: Version bump only for package @​commitlint/cli

v19.0.2

Compare Source

Note: Version bump only for package @​commitlint/cli

v19.0.1

Compare Source

Bug Fixes
  • drop resolve-from, resolve-global and import-fresh, resolve global packages correctly (#​3939) (8793c63), closes #​3938

v19.0.0

Compare Source

Reverts
  • Revert "chore!: minimum node version v20" (2816783)
BREAKING CHANGES

  • migrate to pure ESM

  • feat: migrate to pure ESM

  • chore: update snapshot

  • fix: load parserPreset with another await

  • test: migrate to vitest

  • test: remove no replacement --runInBand test-ci script

  • chore: fix code reviews

  • refactor(load): rewrite resolve logic

  • fix(config-nx-scopes): fix syntax error

  • feat(resolve-extends): add resolveFrom and loadParserPreset

  • feat(load): use resolveFrom and loadParserPreset from resolve-extends

  • test: include only @​commitlint/* packages src in coverage

  • test: explicit import vitest utilities

  • test: remove @​jest/globals from dependencies

  • fix(resolve-extends): resolveFrom output should be platform aware

  • test: restore NO_COLOR to test script

  • chore: fix linting issues

  • fix: should use fileURLToPath instead of pathname for Windows compatibility

  • Apply suggestions from code review

  • fix: should reuse cli instead call yargs()

  • feat(cli): set terminalWidth as wrap to avoid work break on help

  • Update .eslintrc.cjs

  • feat: migrate @​commitlint/config-conventional to pure ESM

18.6.1 (2024-02-13)

Note: Version bump only for package @​commitlint/cli

v18.6.1

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.0.3

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

v19.0.0

Compare Source

Reverts
  • Revert "chore!: minimum node version v20" (2816783)
BREAKING CHANGES

  • migrate to pure ESM

  • feat: migrate to pure ESM

  • chore: update snapshot

  • fix: load parserPreset with another await

  • test: migrate to vitest

  • test: remove no replacement --runInBand test-ci script

  • chore: fix code reviews

  • refactor(load): rewrite resolve logic

  • fix(config-nx-scopes): fix syntax error

  • feat(resolve-extends): add resolveFrom and loadParserPreset

  • feat(load): use resolveFrom and loadParserPreset from resolve-extends

  • test: include only @​commitlint/* packages src in coverage

  • test: explicit import vitest utilities

  • test: remove @​jest/globals from dependencies

  • fix(resolve-extends): resolveFrom output should be platform aware

  • test: restore NO_COLOR to test script

  • chore: fix linting issues

  • fix: should use fileURLToPath instead of pathname for Windows compatibility

  • Apply suggestions from code review

  • fix: should reuse cli instead call yargs()

  • feat(cli): set terminalWidth as wrap to avoid work break on help

  • Update .eslintrc.cjs

  • feat: migrate @​commitlint/config-conventional to pure ESM

18.6.2 (2024-02-14)

Bug Fixes

18.6.1 (2024-02-13)

Note: Version bump only for package @​commitlint/config-conventional

v18.6.2

Compare Source

Bug Fixes

v18.6.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

mantinedev/mantine (@​mantine/core)

v7.6.1

Compare Source

What's Changed
  • [@mantine/core] Fix incorrect focus ring styles in Button.Group and ActionIcon.Group components (#​5736)
  • [@mantine/core] Progress: Fix incorrect border-radius with multiple sections
  • [@mantine/dates] DateTimePicker: Fix minDate and maxDate not being respected in time input (#​5819)
  • [@mantine/core] Switch: Use role="switch" for better accessibility (#​5746)
  • [@mantine/hooks] use-resize-observer: Fix incorrect ref type (#​5780)
  • [@mantine/dates] Fix popoverProps.onClose overriding original component value in DatePickerInput and other similar components (#​4105)
  • [@mantine/core] Fix incorrect Escape key handling in Modal and Drawer components in some cases (#​2827)
  • [@mantine/core] Combobox: Fix incorrect Escape key handling in Modal, Drawer and Popover
  • [@mantine/core] Transition: Fix transition resolving instantly in some cases (#​3126, #​5193)
  • [@mantine/core] Remove loader from the DOM if loading prop is not set on ActionIcon and Button components (#​5795)
  • [@mantine/hooks] use-local-storage: Fix inconsistent default value persistence if getInitialValueInEffect is set (#​5796)
  • [@mantine/core] Select: Fix autoComplete prop not working (#​5813)
  • [@mantine/core] Tabs: Fix incorrect border styles in outline variant
  • [@mantine/core] Checkbox: Fix incorrect indeterminate + disabled styles for outline variant (#​5806)
  • [@mantine/core] SegmentedControl: Fix indicator state not being updated correctly when controlled state changes to a value that is not present in the data array (#​5689)
  • [@mantine/core] Fix incorrect label offset with left label position in Checkbox, Switch and Radio components (#​5823)
  • [@mantine/core] PinInput: Fix updating controlled value to an empty string working incorrectly
  • [@mantine/core] Menu: Fix incorrect role of dropdown elements
New Contributors

Full Changelog: mantinedev/mantine@7.6.0...7.6.1

v7.6.0: 🌟

Compare Source

View changelog with demos on mantine.dev website

Container queries support

You can now use container queries
with Mantine components. rem and em functions from postcss-preset-mantine
are available in container queries staring from postcss-preset-mantine@1.13.0.

.root {
  min-width: rem(200px);
  max-width: 100%;
  min-height: rem(120px);
  container-type: inline-size;
  overflow: auto;
  resize: horizontal;
}

.child {
  background-color: var(--mantine-color-dimmed);
  color: var(--mantine-color-white);
  padding: var(--mantine-spacing-md);

  @​container (max-width: rem(500px)) {
    background-color: var(--mantine-color-blue-filled);
  }

  @​container (max-width: rem(300px)) {
    background-color: var(--mantine-color-red-filled);
  }
}
RadarChart component

New RadarChart component:

import { RadarChart } from '@​mantine/charts';
import { data } from './data';

function Demo() {
  return (
    <RadarChart
      h={300}
      data={multiData}
      dataKey="product"
      withPolarRadiusAxis
      series={[
        { name: 'sales_january', color: 'lime.4', opacity: 0.1 },
        { name: 'sales_february', color: 'cyan.4', opacity: 0.1 },
      ]}
    />
  );
}
FocusTrap.InitialFocus component

FocusTrap.InitialFocus is a new component that adds a visually hidden
element which will receive the focus when the focus trap is activated.
Once FocusTrap.InitialFocus loses focus, it is removed from the tab order.

For example, it is useful if you do not want to focus any elements inside the Modal when it is opened:

import { Button, FocusTrap, Modal, TextInput } from '@&#8203;mantine/core';
import { useDisclosure } from '@&#8203;mantine/hooks';

function Demo() {
  const [opened, { open, close }] = useDisclosure(false);

  return (
    <>
      <Modal opened={opened} onClose={close} title="Focus demo">
        <FocusTrap.InitialFocus />
        <TextInput label="First input" placeholder="First input" />
        <TextInput
          data-autofocus
          label="Input with initial focus"
          placeholder="It has data-autofocus attribute"
          mt="md"
        />
      </Modal>

      <Button onClick={open}>Open modal</Button>
    </>
  );
}
New MantineProvider props

MantineProvider now includes more props to control how styles
are generated and injected. These props are useful if you use Mantine as a headless library
and in test environments.

deduplicateCssVariables

deduplicateCssVariables prop determines whether CSS variables should be deduplicated: if CSS variable has the same value as in default theme, it is not added in the runtime.
By default, it is set to true. If set to false, all Mantine CSS variables will be added in <style /> tag
even if they have the same value as in the default theme.

import { MantineProvider } from '@&#8203;mantine/core';

function Demo() {
  return (
    <MantineProvider deduplicateCssVariables={false}>
      <App />
    </MantineProvider>
  );
}
withStaticClasses

withStaticClasses determines whether components should have static classes, for example, mantine-Button-root.
By default, static classes are enabled, to disable them set withStaticClasses to false:

import { MantineProvider } from '@&#8203;mantine/core';

function Demo() {
  return (
    <MantineProvider withStaticClasses={false}>
      <App />
    </MantineProvider>
  );
}
withGlobalClasses

withGlobalClasses determines whether global classes should be added with <style /> tag.
Global classes are required for hiddenFrom/visibleFrom and lightHidden/darkHidden props to work.
By default, global classes are enabled, to disable them set withGlobalClasses to false. Note that
disabling global classes may break styles of some components.

import { MantineProvider } from '@&#8203;mantine/core';

function Demo() {
  return (
    <MantineProvider withGlobalClasses={false}>
      <App />
    </MantineProvider>
  );
}
HeadlessMantineProvider

HeadlessMantineProvider is an alternative to MantineProvider
that should be used when you want to use Mantine as a headless UI library. It removes all
features that are related to Mantine styles:

  • Mantine classes are not applied to components
  • Inline CSS variables are not added with style attribute
  • All color scheme related features are removed
  • Global styles are not generated

Limitations of HeadlessMantineProvider:

  • Color scheme switching will not work. If your application has a dark mode, you will need to implement it on your side.
  • Props that are related to styles in all components (color, radius, size, etc.) will have no effect.
  • Some components that rely on styles will become unusable (Grid, SimpleGrid, Container, etc.).
  • lightHidden/darkHidden, visibleFrom/hiddenFrom props will not work.
  • Style props will work only with explicit values, for example mt="xs" will not work, but mt={5} will.

To use HeadlessMantineProvider, follow getting started guide and replace MantineProvider with HeadlessMantineProvider.
Note that you do not need to use ColorSchemeScript in your application, it will not have any effect,
you can ignore this part of the guide.

import { HeadlessMantineProvider } from '@&#8203;mantine/core';

function App() {
  return <HeadlessMantineProvider>{/* Your application */}</HeadlessMantineProvider>;
}
Sparkline trendColors

Sparkline now supports trendColors prop to change chart color depending on the trend.
The prop accepts an object with positive, negative and neutral properties:

  • positive - color for positive trend (first value is less than the last value in data array)
  • negative - color for negative trend (first value is greater than the last value in data array)
  • neutral - color for neutral trend (first and last values are equal)

neutral is optional, if not provided, the color will be the same as positive.

import { Sparkline } from '@&#8203;mantine/charts';
import { Stack, Text } from '@&#8203;mantine/core';

const positiveTrend = [10, 20, 40, 20, 40, 10, 50];
const negativeTrend = [50, 40, 20, 40, 20, 40, 10];
const neutralTrend = [10, 20, 40, 20, 40, 10, 50, 5, 10];

function Demo() {
  return (
    <Stack gap="sm">
      <Text>Positive trend:</Text>
      <Sparkline
        w={200}
        h={60}
        data={positiveTrend}
        trendColors={{ positive: 'teal.6', negative: 'red.6', neutral: 'gray.5' }}
        fillOpacity={0.2}
      />

      <Text mt="md">Negative trend:</Text>
      <Sparkline
        w={200}
        h={60}
        data={negativeTrend}
        trendColors={{ positive: 'teal.6', negative: 'red.6', neutral: 'gray.5' }}
        fillOpacity={0.2}
      />

      <Text mt="md">Neutral trend:</Text>
      <Sparkline
        w={200}
        h={60}
        data={neutralTrend}
        trendColors={{ positive: 'teal.6', negative: 'red.6', neutral: 'gray.5' }}
        fillOpacity={0.2}
      />
    </Stack>
  );
}
RichTextEditor tasks extension

RichTextEditor now supports tasks tiptap extension:

import TaskItem from '@&#8203;tiptap/extension-task-item';
import { useEditor } from '@&#8203;tiptap/react';
import StarterKit from '@&#8203;tiptap/starter-kit';
import { getTaskListExtension, RichTextEditor } from '@&#8203;mantine/tiptap';

function Demo() {
  const editor = useEditor({
    extensions: [
      StarterKit,
      getTaskListExtension(TipTapTaskList),
      TaskItem.configure({
        nested: true,
        HTMLAttributes: {
          class: 'test-item',
        },
      }),
    ],
    content: `
        <ul data-type="taskList">
          <li data-type="taskItem" data-checked="true">A list item</li>
          <li data-type="taskItem" data-checked="false">And another one</li>
        </ul>
      `,
  });

  return (
    <div style={{ padding: 40 }}>
      <RichTextEditor editor={editor}>
        <RichTextEditor.Toolbar>
          <RichTextEditor.ControlsGroup>
            <RichTextEditor.TaskList />
            <RichTextEditor.TaskListLift />
            <RichTextEditor.TaskListSink />
          </RichTextEditor.ControlsGroup>
        </RichTextEditor.Toolbar>

        <RichTextEditor.Content />
      </RichTextEditor>
    </div>
  );
}
renderOption prop

Select, MultiSelect, TagsInput and Autocomplete
components now support renderOption prop that allows to customize option rendering:

import {
  IconAlignCenter,
  IconAlignJustified,
  IconAlignLeft,
  IconAlignRight,
  IconCheck,
} from '@&#8203;tabler/icons-react';
import { Group, Select, SelectProps } from '@&#8203;mantine/core';

const iconProps = {
  stroke: 1.5,
  color: 'currentColor',
  opacity: 0.6,
  size: 18,
};

const icons: Record<string, React.ReactNode> = {
  left: <IconAlignLeft {...iconProps} />,
  center: <IconAlignCenter {...iconProps} />,
  right: <IconAlignRight {...iconProps} />,
  justify: <IconAlignJustified {...iconProps} />,
};

const renderSelectOption: SelectProps['renderOption'] = ({ option, checked }) => (
  <Group flex="1" gap="xs">
    {icons[option.value]}
    {option.label}
    {checked && <IconCheck style={{ marginInlineStart: 'auto' }} {...iconProps} />}
  </Group>
);

function Demo() {
  return (
    <Select
      label="Select with renderOption"
      placeholder="Select text align"
      data={[
        { value: 'left', label: 'Left' },
        { value: 'center', label: 'Center' },
        { value: 'right', label: 'Right' },
        { value: 'justify', label: 'Justify' },
      ]}
      renderOption={renderSelectOption}
    />
  );
}
Styles improvements

All Mantine components have been migrated to logical CSS properties
(as a replacement for rtl styles) and :where pseudo-class
(as a replacement for private CSS variables). These changes
should not impact the usage of Mantine components, but now Mantine CSS files have smaller size. For example,
@mantine/core/styles.css now has ~ 8% smaller size (192kb -> 177kb).

Pass props to inner recharts components

You can now pass props down to recharts Bar, Area and Line components
with barProps, areaProps and lineProps props on BarChart, AreaChart and LineChart components.

All props accepts either an object with props or a function that receives
series data as an argument and returns an object with props.

PieChart percent labels

PieChart now supports percent labels:

import { BarChart } from '@&#8203;mantine/charts';
import { data } from './data';

function Demo() {
  return (
    <BarChart
      h={200}
      data={data}
      dataKey="month"
      orientation="vertical"
      yAxisProps={{ width: 80 }}
      barProps={{ radius: 10 }}
      series={[{ name: 'Smartphones', color: 'blue.6' }]}
    />
  );
}
Documentation updates
Help center updates

New articles added to the help center:

Other changes
  • use-list-state hook now supports swap handler
  • form.setFieldValue now supports callback function as an argument
  • px, py, mx and my style props now use logical CSS properties padding-inline, padding-block, margin-inline and margin-block instead of padding-left, padding-right, etc.
  • All components now support me, ms, ps, pe style props to set margin-inline-end, margin-inline-start, padding-inline-start and padding-inline-end CSS properties
  • Tooltip, Popover and other components based on Popover now support floatingStrategy prop to control Floating UI strategy
  • All @mantine/charts components now support children prop which passes children to the root recharts component
  • use-resize-observer and use-element-size hooks now support ResizeObserver options as hook argument
  • Select, MultiSelect and TagsInput now support onClear prop, the function is called when clear button is clicked
  • MultiSelect and TagsInput now support onRemove prop, the function is called with removed item value when one of the items is deselected
  • Redwood template has been updated to the latest redwood version with Vite

v7.5.3

Compare Source

What's Changed
  • [@mantine/core] NumberInput: Fix double border between controls appeared on low resolution screens (#​5753)
  • [@mantine/hooks] use-hotkeys: Fix incorrect HotkeyItem type (#​5705)
  • [@mantine/hooks] use-resize-observer: Fix incorrect ref type (#​5759)
  • [@mantine/core] ScrollArea: Fix offsetScrollbars not working on y-axis (#​5762)
  • [@mantine/core] NavLink: Add collapse Styles API selector (#​5776)
  • [@mantine/hooks] Fixed initial value of the online attribute returned by useNetwork() in Firefox (#​5766)
  • [@mantine/core] PinInput: Fix inputs not being updated with length prop changes
  • [@mantine/core] PinInput: Fix incorrect onComplete behavior (#​5774, #​5771)
  • [@mantine/core] Card: Fix incorrect margins in first and last sections when CardSection component is used instead of Card.Section (#​5742)
  • [@mantine/core] Tooltip: Fix multiline prop not working correctly in Tooltip.Floating component
New Contributors

Full Changelog: mantinedev/mantine@7.5.2...7.5.3

v7.5.2

Compare Source

What's Changed
  • [@mantine/core] ActionIcon: Fix icon width and height defined in % not working correctly
  • [@mantine/core] ScrollArea: Fix offsetScrollbars not working (#​5733)
  • [@mantine/tiptap] Fix initialExternal on RichTextEditor.Link control not working correctly
  • [@mantine/core] FileInput: Fix incorrect extend function type
  • [@mantine/core] PinInput: Fix various issues related to user input and pasting into the input (#​5704)
  • [@mantine/form] Add callback argument support to form.setFieldValue handler (#​5696)
  • [@mantine/core] Add explicit extension to exports to support NodeNext TypeScript resolution (#​5697)
  • [@mantine/hooks] use-list-state: Add swap handler support (#​5716)
  • [@mantine/core] Fix NodeNext TypeScript resolution not working correctly for PolymorphicComponentProps and PolymorphicRef types (#​5730)
  • [@mantine/core] Fix cjs builds unable to resolve third-party dependencies with certain TypeScript settings (#​5741)
  • [@mantine/core] Transition: Fix skew-up transition not working (#​5714)
  • [@mantine/core] Select: Fix active option not being scrolled into view when the dropdown opens
  • [@mantine/core] Menu: Fix unexpected focus trap when keepMounted is false (#​4502)
  • [@mantine/core] ScrollArea: Fix style prop not being passed to the element when used in viewportProps (#​5594)
  • [@mantine/core] Divider: Fix poor color contrast with light color scheme
  • [@mantine/core] Modal: Fix incorrect content border-radius when fullScreen prop is set
  • [@mantine/core] Modal: Fix scroll container not working correctly when ScrollArea is used as a scroll container for a full screen modal
  • [@mantine/notifications] Fix notifications handlers not allowing passing data-* attributes (#​5640)
New Contributors

Full Changelog: mantinedev/mantine@7.5.1...7.5.2

microsoft/playwright (@​playwright/te

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 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, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@netlify Netlify
Copy link

netlify bot commented Mar 1, 2024 •
edited

✅ Deploy Preview for my-react-template ready!

Name Link
🔨 Latest commit a89ef29
🔍 Latest deploy log https://app.netlify.com/sites/my-react-template/deploys/65e11d10aca9f20008ed0c24
😎 Deploy Preview https://deploy-preview-111--my-react-template.netlify.app/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@DuckyMomo20012 DuckyMomo20012 merged commit a000e6a into main Mar 1, 2024
5 checks passed
@DuckyMomo20012 DuckyMomo20012 deleted the renovate/all branch March 1, 2024 02:17
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
@DuckyMomo20012