Skip to content

Bump mixin-deep from 1.3.1 to 1.3.2 #146

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.

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

Merged
merged 1 commit into from
Sep 9, 2019

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 5, 2019

Bumps mixin-deep from 1.3.1 to 1.3.2.

Commits
Maintainer changes

This version was pushed to npm by doowb, a new releaser for mixin-deep since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added the Dependencies Pull requests that update a dependency file label Sep 5, 2019
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/mixin-deep-1.3.2 branch from bceae33 to 6352d2d Compare September 9, 2019 08:34
@kmagiera kmagiera merged commit 8567af0 into master Sep 9, 2019
@kmagiera kmagiera deleted the dependabot/npm_and_yarn/mixin-deep-1.3.2 branch September 9, 2019 08:36
kkafar added a commit that referenced this pull request Jul 16, 2025
…in example (#146)

## Description

- **Remove alternative way of providing `StackContainer` with path
configuration**

It unnecessarily complicates things, we don't need it. In both
approaches we need to specify available screens (paths in current
nomenclature) up front anyway. It is fine to specify just the config.

## Test code and steps to reproduce

`TestScreenStack`

## Checklist

- [ ] Ensured that CI passes
kkafar added a commit that referenced this pull request Jul 16, 2025
…in example (#146)

## Description

- **Remove alternative way of providing `StackContainer` with path
configuration**

It unnecessarily complicates things, we don't need it. In both
approaches we need to specify available screens (paths in current
nomenclature) up front anyway. It is fine to specify just the config.

## Test code and steps to reproduce

`TestScreenStack`

## Checklist

- [ ] Ensured that CI passes
maciekstosio pushed a commit that referenced this pull request Jul 17, 2025
…in example (#146)

## Description

- **Remove alternative way of providing `StackContainer` with path
configuration**

It unnecessarily complicates things, we don't need it. In both
approaches we need to specify available screens (paths in current
nomenclature) up front anyway. It is fine to specify just the config.

## Test code and steps to reproduce

`TestScreenStack`

## Checklist

- [ ] Ensured that CI passes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant