- Entreprise7pro Bootstrap 3 is compatible with jQuery 4, jQuery 3, jQuery 2 and jQuery 1.8+
- Entreprise7pro Bootstrap 3 has CVE fix for CVE-2024-6485 and also for CVE-2025-1647
- What to expect going forward?
- CVE coverage
- Bugfixes
- The possibility of backporting one or more important features from bs4/bs5 into a new branch called 3.5.x.
bower install entreprise7pro/bootstrap --save
composer require entreprise7pro/bootstrap- https://packagist.org/packages/entreprise7pro/bootstrap
- https://packagist.org/packages/entreprise7pro/bootstrap-sass (optional)
npm install entreprise7pro-bootstrap
Bootstrap is a sleek, intuitive, and powerful front-end framework for faster and easier web development.
- Cinder Systems Corp
- Entreprise 7pro.ca Inc.
Originally created by Mark Otto and Jacob Thornton, and previously maintained by the core team with the massive support and involvement of the community.
To get started, check out https://bootstrap.7pro.ca/!
- Quick start
- Bugs and feature requests
- Documentation
- Contributing
- Community
- Versioning
- Creators
- Thanks
- Copyright and license
Several quick start options are available:
- Download the latest release.
- Clone the repo:
git clone https://github.com/entreprise7pro/bootstrap.git. - Consume the CDNs https://bootstrap.7pro.ca
- Install with Composer:
composer require entreprise7pro/bootstrap.
Read the Getting started page for information on the framework contents, templates and examples, and more.
Within the download you'll find the following directories and files, logically grouping common assets and providing both compiled and minified variations. You'll see something like this:
bootstrap/
├── css/
│ ├── bootstrap.css
│ ├── bootstrap.css.map
│ ├── bootstrap.min.css
│ ├── bootstrap.min.css.map
│ ├── bootstrap-theme.css
│ ├── bootstrap-theme.css.map
│ ├── bootstrap-theme.min.css
│ └── bootstrap-theme.min.css.map
├── js/
│ ├── bootstrap.js
│ └── bootstrap.min.js
└── fonts/
├── glyphicons-halflings-regular.eot
├── glyphicons-halflings-regular.svg
├── glyphicons-halflings-regular.ttf
├── glyphicons-halflings-regular.woff
└── glyphicons-halflings-regular.woff2
We provide compiled CSS and JS (bootstrap.*), as well as compiled and minified CSS and JS (bootstrap.min.*). CSS source maps (bootstrap.*.map) are available for use with certain browsers' developer tools. Fonts from Glyphicons are included, as is the optional Bootstrap theme.
Have a bug or a feature request? Please first read the issue guidelines and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.
Note that feature requests must target Bootstrap v3,. We are focused on maintenance and compatibility of bootstrap 3 with modern dependencies like jQuery v4 and most browsers.
Bootstrap's documentation, included in this repo in the root directory, is built with Jekyll and publicly hosted at https://bootstrap.7pro.ca/. The docs may also be run locally.
- If necessary, install Jekyll and other Ruby dependencies with
bundle install. Note for Windows users: Read this guide to get Jekyll up and running without problems. - From the root
/bootstrapdirectory, runbundle exec jekyll servein the command line. - Open
http://localhost:9001in your browser, and voilà.
Learn more about using Jekyll by reading its documentation.
Previous releases and their documentation are also available for download.
Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development.
Moreover, if your pull request contains JavaScript patches or features, you must include relevant unit tests. All HTML and CSS should conform to the Code Guide, maintained by Mark Otto.
compatible with jQuery 4. We are focusing our efforts on Bootstrap v3, the future of the entreprise7pro bootstrap release of the framework is here.
Pull requests which add new features (rather than fix bugs) should target Bootstrap v3 (the v3-dev git branch).
Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at https://editorconfig.org/.
Get updates on Bootstrap's development and chat with the project maintainers and community members.
ootstrap` channel.
- Implementation help may be found at Stack Overflow (tagged
entreprise7pro-bootstrap). - Developers should use the keyword
bootstrapand orentreprise7proon packages which modify or add to the functionality of Bootstrap when distributing through npm or similar delivery mechanisms for maximum discoverability.
For transparency into our release cycle and in striving to maintain backward compatibility, Bootstrap is maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we'll adhere to those rules whenever possible.
See the Releases section of our GitHub project for changelogs for each release version of Bootstrap.
sudo apt install nodejs npmsudo apt install node-grunt-clibundle exec grunt --forceopenssl dgst -sha384 -binary dist/js/bootstrap.min.js | base64openssl dgst -sha384 -binary dist/css/bootstrap-theme.min.css | base64openssl dgst -sha384 -binary dist/css/bootstrap.min.css | base64npm run release- npm run release-zip
Maintainer release checklist (example: v3.4.10). Substitute the new
version in the commands for future releases. Prepare releases on v3-dev,
the default branch; there is no need to merge into main just to publish.
-
Prepare the version. From the repository root, check the branch and working tree:
git switch v3-dev git status --short
Synchronize version metadata in
package.json,package-lock.json,package.js,_config.yml, and the JavaScript component version headers andConstructor.VERSIONconstants. Review any changes carefully; the existingnpm run change-versioncommand performs broad replacements. -
Test and build. Install dependencies if necessary, then run:
npm ci npx grunt test-js npm run release git diff --check git status --short
test-jsruns lint/style checks and the Karma browser tests; local Snap Firefox may need a writable temporary-profile location if the Gruntfile workaround has not been applied.npm run releaseproduces the compiled distribution, documentation, SRI hashes, and the release ZIP. Do not runnpm run release-zipa second time. Inspect the generated artifacts. -
Commit, push, and verify CI. Commit only intended changes (avoid local
.tgzfiles and other unrelated archives), pushv3-dev, and verify the GitHub Actions checks for that commit:git add -u # Add any intended new files explicitly: git add <path> git diff --cached --check git diff --cached --stat git commit -m "Release v3.4.10" git push origin v3-dev
Skip the commit if everything is already committed. Do not tag until the relevant CI checks pass and release contents are final.
-
Tag the release at the verified commit:
git status --short git tag -a v3.4.10 -m "Bootstrap v3.4.10" git push origin v3.4.10Do not move or reuse a published tag.
-
Publish the GitHub Release at New release: select
v3.4.10, add release notes, optionally attachbootstrap-3.4.10-dist.zip, and publish as the latest stable release. A Git tag alone does not create a GitHub Release unless an automation explicitly handles it. -
Publish to npm, after verifying no workflow already published the version, using the manual CLI authentication procedure below. Package name:
entreprise7pro-bootstrap(notentreprise7pro/bootstrap). Check availability, review contents, publish once, and verify the result:npm login --auth-type=web npm view entreprise7pro-bootstrap@3.4.10 version npm pack --dry-run npm pack npm publish --access public npm view entreprise7pro-bootstrap@3.4.10 version
-
Check Packagist and the documentation site. Verify that
entreprise7pro/bootstraplists the new Git tag; if not, sign in and select Update. Confirm bootstrap.7pro.ca reflects the new release (deploy manually if necessary).
Use the terminal login method, rather than npm's browser-login default:
npm login --auth-type=web
npm whoamiSign in with the maintainer account that has publishing rights for
entreprise7pro-bootstrap (josepholstad); npm whoami verifies which
account the CLI is using. Legacy login still requires any applicable 2FA
verification. If npm opens a passkey/security-key prompt during account setup
or authorization, a supported phone may offer Use PIN / Try another
way instead of a fingerprint. A government smart card is not necessarily
a compatible FIDO2 security key. Never commit npm credentials or tokens.
Before publishing, inspect the tarball and check whether the version already exists on npm:
npm pack --dry-run
npm view entreprise7pro-bootstrap@3.4.10 version
npm publish --access publicSubstitute the current release version for 3.4.10. A 404/not-found result
from npm view before publication is expected for a new version; if the
version already exists, do not publish it again. E403 requiring 2FA
means login alone is insufficient: satisfy the account's current publishing
security requirements, then retry. The command-line login method does not
bypass publishing security checks.
Thanks to BrowserStack for providing the infrastructure that allows us to test in real browsers!
Stephen Mulvihill
Joseph Olstad
Mark Otto
Jacob Thornton
Entreprise 7pro.ca Inc. copyright 2024-2026. Currently released under the MIT license. Docs released under Creative Commons. Code and documentation copyright 2011-2019 Twitter, Inc. Twitter Code previously released under the MIT license.