Automate deployment of new versions

[n-bernat]

Summary of changes

pubspec.yaml

• Bumped version constraints, so the package supports Dart 3
• Replaced lint with the official flutter_lints package and fixed a config file for lints
• Removed dependency on html

generate_fonts.dart

• Fonts are now generated based on the info.json file
• In the future, it would be probably preferable to replace it with a bash script because installing Dart to do such a simple thing is a waste of resources

lucide_icons.dart

• It will be replaced with icons generated by generate.yaml workflow (https://github.com/n-bernat/lucide-flutter/commit/36fad92853b182884f95fdfc8e7deed45f2cfef3)

generate.yaml

• (The whole magic happens in this action)
• It's run once a day and fetches the latest release from lucide-icons/lucide
• If there was a release, it downloads an icon font with info.json and copies those files to assets
• After that, it runs the generator and bumps the version to match the one from the main repository
• At the end, it commits changes and creates a new tag
• ⚠️ Keep in mind that this workflow requires a repository-scoped deploy key, because:

  operations act by Github-actions bot cannot trigger a new workflow run ~ https://github.com/orgs/community/discussions/27028

publish.yaml

• (The final piece of this configuration)
• Pub.dev only allows automated publishing from GitHub Actions when the workflow is triggered by pushing a git tag to GitHub
• Uses --force flag and separate steps to install Dart and Flutter due to some tooling issues https://github.com/dart-lang/setup-dart/issues/68

Pub.dev configuration

In https://pub.dev/packages/lucide_icons/admin someone with admin rights has to enable publishing from GitHub Actions

---

Example run: https://github.com/n-bernat/lucide-flutter/actions/runs/8088943739

Example changes: https://github.com/n-bernat/lucide-flutter/commit/935fbf8a4599e84fdfe8f4f69e2012a4e1a60b24