v1.1.0

Welcome Folks and Stargazers,

We are excited to announce the next update to the Pulsar Package Backend!

This update was able to include many fixes, and many new features for the backend, with a heavy focus on improving the testing framework to allow bugs to be caught earlier, easier, and faster. Thanks a ton to all of those who helped implement and plan these changes!

As always happy coding, enjoy the stars!

From the Pulsar Backend Team

• Removed nearly all static data returns during dev runs, to reduce chance of bugs being missed.
• Removed dev server support.
• Fixed an issue where delivery time generated badges wouldn't appear on a list.
• Implemented object builder patterns, to reduce verbosity and knowledge needed throughout the codebase.
• Improved errors returned during a new package version publish.
• Improved internal log injection safety checks, to further mitigate any malicious logs.
• Added a new service filter to the /api/packages endpoint, to filter a package based off the services it consumes or provides.
• Added badge support, and added automated Made for Pulsar! badges to packages.
• Fixed an issue where the package data column wouldn't be updated correctly during a new version publish.
• Refactored all /packages endpoints, to make future changes and fixes easier.
• Improved errors returned in some situations to increase transparency on the server's logic.
• Fixed an issue that would stop the rename query parameter from being handled correctly.
• Fixed issue that could cause package download URL's to not resolve properly.
• Improved search handling to support spaces among other stop words to still resolve the expected search query.
• Deprecate /api/packages/:packageName/versions/:versionName/events/uninstall. This endpoint no longer has any effect, but will still return a successful query to avoid user impact.
• Refactored the existing testing platform
• Refactored all interactions with GitHub, Git, and provided the base system to support multiple VCS services in the future.

v1.0.1

Welcome Folks and Stargazers,

We are proud to welcome the next update to the Pulsar Package Backend!

This update comes with many fixes and improvements over the last version, but of course we are nowhere near complete with the list of improvements we want to make! Getting things updated the way we have comes as a labor of love from the dedicated Backend team at Pulsar with special thanks to @Digitalone1, @Spiker985 and @kyjus25!

Within this version are some of the highlights:

• Huge improvements to package version management
• Hugely improved security during OAuth Signup
• Fixes to Pagination
• Rate Limiting to protect our servers
• HTTP OPTIONS support for all endpoints
• Fixes to Deleting package versions
• Swagger Documentation hosted alongside the API
• Fixed the possibility of a Supply Chain Attack to end users
• Upgraded NodeJS to newest version as well as many updates to the underlying packages in use for the project

There's much more to come in terms of updates, especially focusing on supporting package maintainers as much as we can, but for now we hope these changes can improve the Pulsar Community Package experience and feel free to take a look at the newest updates via the Package Registry Frontend Website or via the Pulsar Package API.

As always happy coding, enjoy the stars! 💫

From the Pulsar Backend Team

v1.0.0

Welcome Folks and Stargazers,

Finally we can welcome version 1 of the Pulsar/Atom Backend!

This has been a long journey that couldn't have been possible without the contributions both within and outside of this repo, and the whole Pulsar team has my thanks.

This release of the Backend includes full feature parity with the now sunset Atom.io Closed Source Backend Server. After a full archival of all Atom Community Packages, and reverse engineering of their backend we finally have it's drop in replacement.

This Backend Server supports all documented and undocumented endpoints that were originally available on Atom, and should support all interactions with APM, PPM the Atom application, the Pulsar application, and any other unknown 3rd party services that integrated with the backend. Essentially it should look like nothing has changed.

That is with one small caveat, Logging in. If you'd like to read more on how to create an account for Pulsar take a look at the docs.

This new version is freshly available on https://api.pulsar-edit.dev so feel free to take a look and let me know what you think! Happy coding, enjoy the stars! 💫

• The Pulsar Backend Team