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.

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

Update demogroup #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update demogroup #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 2, 2018

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
github.com/pkg/errors require minor v0.7.0 -> v0.9.1 age adoption passing confidence
lodash (source) dependencies patch ^3.0.0 -> ^3.10.1 age adoption passing confidence

Release Notes

pkg/errors

v0.9.1: errors 0.9.1

Compare Source

pkg/errors 0.9.1 is a bug fix release for errors 0.9.0. This restore the previous behaviour on Cause method, this behaviour was changed on the PR: #​215 and many breaking changes was produced by that.

v0.9.0: errors 0.9.0

Compare Source

errors 0.9.0 is a preparation release for a 1.0 final release. Also we were working on removing support for Go 1.8, 1.9 and 1.10 and earlier, and become compatible this package with new way of errors on Go 1.13.

We tried to move into runtime.CallerFrames but this was not possible, you can show the explanation here: Issue 188.

The motivation for do the backward compatible this package with Go 1.13 is that you can migrate the easy way for this to the new way.

Now you could use the methods, Is and As, and the Unwrap() interface like on the standard library.

The method Cause is now compatible with fmt.Errorf("%w", err) and with the Unwrap() interface.

On the same way the methods related with wrapping on this package now are compatible with Cause and Unwrap() interface.

Improvements

Bugs fixed

  • .travis.yml Adjust Go versions. Thanks @​komuw, @​aperezg
  • minor fix in an example to print Stack Trace. Thanks @​bep.
  • Remove not necessary code.
  • Clean up documentation. Thanks @​seh.

v0.8.1: errors 0.8.1

Compare Source

pkg/errors 0.8.1 is a bug fix release for errors 0.8.0. It will be the last version to support Go 1.8 and below. pkg/errors 0.9 and above will require Go 1.9 for the new runtime.CallersFrames API.

pkg/errors 0.8.1 also adds one new feature, errors.WithMessagef. Ideally this would be held over til 0.9, but that complicates the switch to runtime.CallersFrames.

Improvements

Bugs fixed

v0.8.0: errors 0.8.0

Compare Source

What's new since version 0.7.1

errors 0.8.0 decomposes Wrap (and Wrapf) into their component operations, namely adding a message to an error, and adding a stack trace to an error, which were previously merged into a single operation.

This is accomplished by adding two top level functions, errors.WithMessage and errors.WithStack, and rewriting Wrap and Wrapf in terms of these operations.

The motivation for this change was need to treat each of the following operations as distinct:

  • Adding a context message to an existing error without altering the stack trace.
  • Adding a stack trace to an existing error without the requirement of adding an additional message.
  • Retrieving the immediate cause of an error; popping one element of the error stack.

The addition of WithStack and WithMessage increases the surface area of this package by two methods, after long discussions at GopherCon 2016 it was felt strongly that destructuring the operation of Wrap and Wrapf was necessary.

For the moment Wrap and Wrapf remain, but depending on your feedback may be deprecated in future releases. Please leave comments via the issue link.

Thanks to @​nmiyake and @​fabstu for their assistance in preparing this release.

Bug fixes

v0.7.1: errors 0.7.1

Compare Source

What's new since version 0.7.0

0.7.1 is a minor release in the 0.7 series which contains bugfixes, documentation improvements and cleanups and some internal refactoring.

Improvements

  • Rename StackTrace interface to stacktracer in docs and examples.
  • Capitalise first letter of trace in examples. Thanks @​jongillham
  • Wrapped errors now print full stacktrace.
  • Documentation improvements, #​69. Thanks @​AlekSi
  • Added benchmarks comparing stack trace performance. Fixes #​72. Thanks @​kardianos

Bug fixes

  • Fix %q format for wrapped errors. Thanks @​greensnark
  • Remove trailing newline from LICENSE file. Thanks @​vbatts
  • Tests now pass when pkg/errors is vendored. Fixes #​77. Thanks @​exp
  • Fix the %q format for errors so it puts "" around the output (caused by a bug introduced between 0.7.0 and 0.7.1). Thanks @​ncw

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate renovate bot force-pushed the renovate/demogroup branch from 01b9244 to eed3e62 Compare January 5, 2019 03:02
@renovate renovate bot force-pushed the renovate/demogroup branch from eed3e62 to c4d93d4 Compare January 18, 2020 12:57
@renovate renovate bot force-pushed the renovate/demogroup branch from c4d93d4 to f0b1d10 Compare March 6, 2020 21:48
@renovate renovate bot changed the title Update demogroup Update dependency lodash to ^3.10.1 Feb 10, 2021
@renovate renovate bot changed the title Update dependency lodash to ^3.10.1 Update demogroup Apr 26, 2021
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant