Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

v0.19.8 dist not up to date #2079

Open
LionelClaudon opened this issue Nov 13, 2017 · 2 comments
Open

v0.19.8 dist not up to date #2079

LionelClaudon opened this issue Nov 13, 2017 · 2 comments

Comments

@LionelClaudon
Copy link

Bug description:

The dist/ folder of tagged version v0.19.8 does not contain v0.19.8 compiled code but v0.19.7
Installing angular-ui-select v0.19.8 from any dependency management tool and pointing to dist/ directory will not contain the actual v0.19.8 code.

Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS

Angular: /

UI-Select: v0.19.8

Bootstrap/Select2/Selectize CSS (if applicable): /

@Greenek
Copy link

Greenek commented Nov 14, 2017

You can use my fork, it has build with all recent changes.

"angular-ui-select": "Greenek/ui-select#header-footer-2"

@aaronroberson
Copy link
Contributor

@Jefiozie I no longer have permissions to merge or commit to master. To publish a new release, please follow these instructions (for maintainers only):

To release a new version, please follow these steps:

  1. Bump the version
    Run gulp recommendedBump to increment the version in package.json and elsewhere.

  2. Update the changelog
    Run gulp changelog to update the changelog based on the conventional commit messages. You may want to visually inspect the changelog after to ensure that it was generated as expected.

  3. Add and commit your changes
    The gulp commands are not working as-is for these operations. Manually run git add . && git commit -am "chore(release): bump package version and update changelog".

  4. Tag the commit with the package version
    Either run gulp tag or manually view the new version in package.json and run git tag vX.X.X where X.X.X is the version number.

  5. Push the commits and tag to remote
    Either run gulp push or manually run git push && git push origin master --tags if the gulp command doesn't work.

  6. Publish to npm
    I don't recall if Travis CI is working in regard to auto-publishing new versions. If upon merge and push, Travis doesn't publish a new version to npm, you can publish it manually. To do so, run npm publish after logging into npm via npm login and entering your npm credentials.

All of this is supposed to be encapsulated in a single gulp command gulp bump. With a couple minor updates, this can be accomplished.

glutentag pushed a commit to glutentag/ui-select that referenced this issue Aug 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants