# Beats with golang version **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [September 18, 2017, 10:41am UTC](https://discuss.elastic.co/t/beats-with-golang-version/100855 "2017-09-18T10:41:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![caibaoying](https://avatars.discourse-cdn.com/v4/letter/c/dc4da7/32.png) [@caibaoying](https://discuss.elastic.co/u/caibaoying)\ **Post date:** [September 18, 2017, 10:41am UTC](https://discuss.elastic.co/t/beats-with-golang-version/100855/1 "2017-09-18T10:41:03Z")
Two month ago, I create my beats according to beats-5.4.3. I installed go 1.7.6. why now it need 1.8.3. Is each version of the beats with a different go version? according to: [https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html](https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html) ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [September 19, 2017, 6:40pm UTC](https://discuss.elastic.co/t/beats-with-golang-version/100855/2 "2017-09-19T18:40:07Z")
If you are using a vendored copy of elastic/beats@v5.4.3 (from a release tag) then the Go version requirement should not change even if the upstream project moves to a new version. If you base your project on a branch there are no guarantees. The project will continue to update to new versions of Go to receive bug fixes, security updates, performance enhancements, and new libraries. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 17, 2017, 6:40pm UTC](https://discuss.elastic.co/t/beats-with-golang-version/100855/3 "2017-10-17T18:40:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.