Download the PHP package oi-lab/oi-laravel-changelogs without Composer

On this page you can find all versions of the php package oi-lab/oi-laravel-changelogs. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package oi-laravel-changelogs

OI Laravel Changelogs

Latest Version on Packagist Total Downloads Tests

The journal of what was fixed and what was improved in your application, kept as markdown in the repository and read on a screen inside the application. One file per entry, written in the same pull request as the work it describes, reviewed with it and deployed with it — no table, no migration, and nothing that has to be regenerated by hand. The package brings the reader, two artisan commands to write and to police the entries, and a set of Inertia/React stubs you install into your own application and then own outright.

Features

How It Works

The package never writes an entry at runtime and has no endpoint that could. Reading is three objects deep:

Object What it is
ChangeLogRepository parses the directory, caches the parse under a fingerprint of it, and answers the list, one entry, and the two either side of it
ChangeLogEntry one parsed file: slug, title, date, type, tags, commits, the opening paragraph, the body
ChangeLogMarkdown the CommonMark converter, kept as a singleton because it is expensive to build and holds nothing

Two shapes leave the server rather than one. ChangeLogRowData is what the list column draws — frontmatter and the opening paragraph — and there may be a hundred of them on a page. ChangeLogEntryData is the entry being read, with its content in whichever form the configured engine asked for. Sending the second shape for every row would put the whole journal on the wire to draw a column 24rem wide.

The screen is one page behind two routes. change-logs.show answers json to a fetch and the whole page to an Inertia visit or a cold browser, so the pane the reader swaps and the page a pasted link opens can never drift apart.

Requirements

Installation

Then run the installer, which asks who may read the journal, where the markdown should be converted, and writes the screen into your application:

It publishes the config, creates the change log directory with one example entry, installs the React files, and offers to add the Shadcn UI components the screen draws with. Everything it writes is yours afterwards — the package renders nothing itself.

Visit /change-logs.

Publish only the configuration

Configuration

Set route.enabled to false to keep the reader and declare your own routes against ChangeLogController — inside an authenticated console group, for instance.

Usage

Write an entry

The commit has to exist before the entry can name it, so: commit the fix, then open the entry.

With no --commit, it fills in HEAD — the commit you just made. The file lands at resources/markdown/change-logs/2026-09-12-the-dashboard-came-back-blank.md with its frontmatter written and two placeholders where the prose goes:

An entry is a subject, not a commit: three commits fixing one thing are one entry with three hashes in its commits:.

Check the format

It names everything wrong with every file — a date the file name disagrees with, a tag that is not lowercase, an opening paragraph outside the word bounds, a TODO left in the text — and ends by printing the tags in use with how many entries each one holds, which is how you spot two spellings of one subject.

The screen skips a malformed file rather than throwing on it, so put the checker in your test suite and a file that would silently vanish fails the build instead:

Read the journal somewhere else

The Published Screen

The installer writes, and you own:

Only the renderer you chose is installed, and the import of the other one is taken out of change-log-detail.tsx — an unused import of react-markdown is a dependency you would have to install to build.

The layout is the neutral one, and the page names it at the bottom:

Point it at your application's own layout, keeping the two constraints the neutral one carries: cap the wrapper at h-svh and let min-h-0 through. An application shell is usually min-h-svh, a floor — and a pane asked to scroll inside a floor never does.

TypeScript Interfaces

The two Data classes are what oi-laravel-ts generates from, so the published types.ts can be replaced by your generated interfaces:

AI Assistant Skills

The package ships a skill teaching an AI assistant when an entry is owed, how one entry covers one subject, and the format the checker enforces. Install it into the host application:

It is the skill to activate right after committing a fix — before the task is considered done.

Testing

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

When contributing:

  1. Write tests for new features
  2. Ensure all tests pass: vendor/bin/pest
  3. Follow existing code style
  4. Update documentation as needed

License

The MIT License (MIT). Please see the License File for more information.

Credits

Olivier Lacombe - Creator and maintainer

Olivier is a Product & Technology Director based in Montpellier, France, with over 20 years of experience innovating in UX/UI and emerging technologies. He specializes in guiding enterprises toward cutting-edge digital solutions, combining user-centered design with continuous optimization and artificial intelligence integration.

Projects & Resources:

Support

For support, please open an issue on the GitHub repository.


All versions of oi-laravel-changelogs with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/cache Version ^11.0|^12.0|^13.0
illuminate/console Version ^11.0|^12.0|^13.0
illuminate/contracts Version ^11.0|^12.0|^13.0
illuminate/filesystem Version ^11.0|^12.0|^13.0
illuminate/http Version ^11.0|^12.0|^13.0
illuminate/pagination Version ^11.0|^12.0|^13.0
illuminate/routing Version ^11.0|^12.0|^13.0
illuminate/support Version ^11.0|^12.0|^13.0
league/commonmark Version ^2.0
spatie/laravel-data Version ^4.23
symfony/yaml Version ^6.0|^7.0|^8.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package oi-lab/oi-laravel-changelogs contains the following files

Loading the files please wait ...