Update dependency source_gen to v1 - abandoned

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
source_gen	dependencies	major	^0.9.5 -> ^1.0.0

---

Release Notes

dart-lang/source_gen

v1.2.7

Compare Source

• Update the value of the pubspec repository field.
• Require Dart SDK version 2.18.
• Fix type-checking mixin elements with TypeChecker.

v1.2.6

Compare Source

• Add support for a preamble option to combining_builder.

v1.2.5

Compare Source

• Fix another issue with overly specific types.

v1.2.4

Compare Source

• Fix overly-specific cast.

v1.2.3

Compare Source

• Require analyzer: '>=4.6.0 <6.0.0'
• Require sdk: '>=2.17.0 <3.0.0'

v1.2.2

Compare Source

• Enable the fix for single cascade statements when formatting Dart code.
  • Individual builders can opt out of this by providing a custom formatOutput
    function to the PartBuilder or LibraryBuilder constructors.
• Allow analyzer version 4.x.

v1.2.1

Compare Source

• Allow reviving constants which are static fields defined on the class which
  represents their type. Previously we checked this pattern only for enums,
  however there are enum-like usages in classes which are not enums.
• Allow the latest version of package:analyzer.

v1.2.0

Compare Source

• Include the LibraryElement in LibraryReader.allElements,
  LibraryReader.annotatedWith, and LibraryReader.annotatedWithExact. Run
  GeneratorForAnnotation generators on library elements when the library
  statement has the annotation.
• Add support for build_extensions configuration to the PartBuilder and
  LibraryBuilder. You must forward the BuilderOptions object to the super
  constructor for this to work.
• Fix a bug finding source locations for reporting unresolved annotations on
  parameters.
• Fix a bug checking for part statements on Windows.

v1.1.1

Compare Source

• Drop dependency on package:pedantic.

v1.1.0

• Add the build_extensions option to combining_builder, allowing output
  files to be generated into a different directory.

v1.0.5

• Fix a bug with reviving constant expressions which are fields defined on a
  different class than their type (but in the same library).

v1.0.4

Compare Source

• Fix warnings with latest analyzer, require analyzer 2.x.

v1.0.3

Compare Source

• Allow the latest version of package:analyzer.

v1.0.2

Compare Source

• Fix TypeChecker.fromRuntimeType for types that come from non-package uris.

v1.0.1

Compare Source

• Improve the error message for a missing part directive.
• Upgrade to package:analyzer version 1.7.0.

v1.0.0

Compare Source

• Migrate to null safety.
• Drop deprecated APIs:
  • ConstantReader.isAny.
  • ConstantReader.anyValue.
  • LibraryReader.classElements.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• 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]

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.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.