Generate release & migration markdown from JSON
Salesforce API Library for JavaScript
Salesforce API Library for JavaScript
Migration tooling for contentful
Convert Domain Names correctly from IDN to Punycode and vice-versa and offer TR46 processing.
Merge several Mochawesome JSON reports
Polyfill for Temporal (https://github.com/tc39/proposal-temporal), an ECMA TC39 Stage 3 proposal
Vue 3 compatibility build for Vue 2
Microsoft Application Insights Common JavaScript Library
A react component toolset for managing animations
Component testing utils for Vue 3.
Dedicated types library for ramda
Syntax highlighting in your terminal
JSON Web Token implementation (symmetric and asymmetric)
A Component Library for Vue 3
[](https://circleci.com/gh/ReactiveX/rxjs/tree/6.x) [](http://badge.fury.io/js/%40reactivex%2Frxjs) [](https://www.npmjs.com/package/ts-proto) [](https://github.com/stephenh/ts-proto/actions)
Reactive Extensions for modern JavaScript
A Storybook builder to dev and build with Vite
SwaggerJS - a collection of interfaces for OAI specs
Webpack plugin for modifying modules source
Microsoft Application Insights Core Javascript SDK
Provides a clean way to handle updates to seed data post-launch.
Allows us to cleanly handle updates to seed data post-launch.
Capistrano task for rolling back DB migrations to the previous release version. It assumes that the schema.rb is checked in with the correct version into the repository. Reads the version from the schema.rb file and runs the db:migrate with that task
RuboCop has many breaking changes between releases. This tool migrates your RuboCop config, making updating RuboCop easier.
For project stability it's a common practive to release db migrations separated from other code changes. This pronto runner helps to enforce this. Also checks other migration PR basic sanity things.
Our goal is that you can migrate large forms to OnForm incrementally, without having to refactor large amounts of code in a single release.
Write reactive web applications using familiar Ruby syntax and patterns. ⚠️ WARNING: This gem has been renamed to 'ruwi' starting from v0.10.0. Please migrate to the 'ruwi' gem. See https://github.com/t0yohei/ruby-wasm-ui/releases/tag/v0.10.0 for migration details.
Build-time DSL (routes, schema, models, migrations), codegen pipeline, CRuby dev loop, and a `fresco new` generator. Targets Spinel for release builds.
- xcsims: Delete all simulators and recreate one for each compatible platform and device type pairing. - sync-git-remotes: Make sure all your GitHub repos are cloned into a given directory and keep them synced with upstream. Forks are maintained with a remote for both the fork and upstream, both remotes' default branches are tracked in local counterparts, and the upstream default branch is also pushed to the fork. - changetag: Extract changelog entries to write into git tag annotation messages. - prerelease-podspec: Branch and create/push a release candidate tag, modify the podspec to use that version tag, and try linting it. - release-podspec: Create a tag with the version and push it to repo origin, push podspec to CocoaPods trunk. - revert-failed-release-tag: In case `release-podspec` fails, make sure the tag it may have created/pushed is destroyed before trying to run it again after fixing, so it doesn't break due to the tag already existing the second time around. - bumpr: Increment the desired part of a version number (major/minor/patch/build) and write the change to a git commit. - clean-rc-tags: deletes any release candidate tags leftover after prerelease testing. - migrate-changelog: for a changelog adhering to [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), move any contents under Unreleased to a new section for a new version with the current date.
# Squash Migrations Periodically squash migrations to reduce overhead of the `db:migrate` Rake task. ## Creating a release 1. Create a new pull request that: - Bumps the version in `rails-squash-migrations.gemspec` - Updates `CHANGELOG.md` to include all noteworthy changes, the release version, and the release date. 2. After the pull request lands, checkout the most up to date `main` branch and build the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem build ``` 3. Publish the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem push rails-squash-migrations-X.Y.Z.gem ``` 4. Create and publish a git tag: ```console $ git tag X.Y.Z $ git push https://github.com/Pioneer-Valley-Books/rails-squash-migrations.git X.Y.Z ```
DEPRECATED — this gem has been renamed to debug-mcp. Install 'debug-mcp' (a drop-in replacement) instead, and update any MCP client config that references 'girb-mcp' / 'girb-rails' to 'debug-mcp' / 'debug-rails'. This release is a deprecation shim that depends on debug-mcp and forwards the executables to it; it will not receive further updates. See https://github.com/rira100000000/debug-mcp for migration details.
["This gem adds the integration for the nobrainer gem in Capistrano.\n\nIt creates the indexes automatically and run the database migration if any (WARNING: You need to use the zedtux's nobrainer fork in order to use migration scripts until it get merged).\n\n| Feature | capistrano-nobrainer version |\n| --------------------------- | ----------------------------- |\n| Nobrainer indexes creation | 0.2.0 |\n| Nobrainer migration scripts | 0.3.0 |\n\nSo if you don't use migration scripts, stick on version 0.2.0.\n\n## Installation\n\nAdd this line to your application's Gemfile:\n\n```ruby\ngem 'capistrano-nobrainer', '~> 0.2', require: false\n```\n\nAnd then execute:\n\n $ bundle install\n\nOr install it yourself as:\n\n $ gem install capistrano-nobrainer\n\n## Usage\n\nAdd the following require to your `Capfile`:\n\n```ruby\nrequire 'capistrano/nobrainer'\n```\n\n## Development\n\nAfter checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.\n\nTo install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).\n\n## Contributing\n\nBug reports and pull requests are welcome on GitHub at https://gitlab.com/zedtux/capistrano-nobrainer. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://gitlab.com/zedtux/capistrano-nobrainer/blob/master/CODE_OF_CONDUCT.md).\n"]
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.