Hey, I would like to have the extension, unfortunately it is no longer on Github. Can you maybe re-upload them?

Using version 1.2 for serakoi/flarumstaffbadge
./composer.json has been updated
Running composer update serakoi/flarumstaffbadge
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals

[RuntimeException]
git was not found in your PATH, skipping source download

require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [<packages>]...

    hover the author removed the git repository. There's no way to get it back, that's also why the Abandoned tag was added.

    Should anyone have this extension currently installed, please make a zip archive of the vendor folder where it sits in and publish it so that it can be adopted and republished by the community.

        luceos Should anyone have this extension currently installed, please make a zip archive of the vendor folder where it sits in and publish it so that it can be adopted and republished by the community.

        Here you go

            hover you can't, the extension was removed. You will have to wait until someone picks it up, re-creates it with the archive that I have provided and publishes it on Packagist so that Composer may require & install it.

                hover luceos wrote that it's up to the community to re-upload the extension. Of course care should be given to the license terms (MIT-licensed extensions can be re-published by anybody as long as the original license file is included, so it's usually fine). While there is no requirement for extension publishers to provide support, re-publishing an abandoned extension often comes with the expectation that the new developer will take on the care of the extension, so most developers like myself won't just re-publish an extension unless it's part of a paid job.

                As the Flarum Foundation or staff member of the forum, there is unfortunately nothing we can do about deleted packages. Packagist and GitHub are the most popular way to distribute Flarum extensions and we can't prevent people from removing packages, even if the license allows re-distributing the code.

                @BAANAN if you could delete the packages from Packagist or mark them abandoned it would be nice. Removing the package from GitHub but not Packagist creates all kinds of annoying issues since Packagist still believes the code can be found on GitHub. Packagist doesn't actually host any code, it just tells Composer to download the zipped files from GitHub.

                In the future Flarum might have an extension marketplace where we have control over the distributed files, but this is still a long time away.

                    Provided "as is" as a temporary solution:

                    composer remove serakoi/flarumstaffbadge
composer require luceos/flarum-ext-staff-badge:"*"

                    Please understand I do not provide support for this fork (extension). If it's broken, get someone to properly fork my repository: https://github.com/luceos/flarum-ext-staff-badge

                    clarkwinkelmann In the future Flarum might have an extension marketplace where we have control over the distributed files, but this is still a long time away.

                    I'll consider storing a tarball of the latest version for all extensions with Extiverse. That should help gracefully saving extensions that get dropped by their authors.

                        luceos

                        I'll consider storing a tarball of the latest version for all extensions with Extiverse. That should help gracefully saving extensions that get dropped by their authors.

                        Actually quite a nice idea šŸ™‚

                          luceos I'll consider storing a tarball of the latest version for all extensions with Extiverse

                          I actually already have cached tarballs of all extensions and their versions inside of the Lab javascript parser. Just no way to easily get them out, but it's all there in a MediaLibrary relationship.

                          The downside of tarballs is that if done "correctly", they don't contain the javascript source code (or less commonly, test files). Which is a huge handicap for bugfixing or ongoing development, since this can't be easily reverse-engineered. The best would be a full git tree backup.

                            14 days later

                            Hey, as of now this extension will not be supported/maintained by me anymore.

                            This is because I have no real time to check the extensions due to work.
                            Sorry šŸ™

                            (Might pick this one up in the far future though...)

                              2 months later

                              BAANAN Hello brother, i really need Staff Badge Extension I'll pay for it. Please help me to get this extension.

                                  13 days later

                                  BAANAN hey! Do you happen to have the GitHub repo for this still? Iā€™d be eager to see if I can perhaps submit a PR and keep this one going šŸ˜ƒ